cluther wrote:
> Here's a good way to troubleshoot zenhub.
>
> 1. Stop zenoss (zenoss stop)
> 2. Start zeo (zeoctl start)
> 3. Run zenhub in the foreground (zenhub run -v 10)
> 4. In another terminal session run zenperfsnmp in the foreground
> (zenperfsnmp run -v 10)
> 5. Look in zenhub's terminal window for errors after you start
> zenperfsnmp
>
> This gives you the fullest view of what's going on with a minimum of
> other distractions.
So I did what you said and I have the full view, but I'm not sure what it is
telling me (if anything). Here's the dump from zenhub:
Code:
DEBUG:zen.Events:EventClassInst=Start
DEBUG:zen.DbConnectionPool:Creating a new connection; Pool size: 0
DEBUG:zen.Events:update status set clearid = '7f0000013633da45ffffea8' where
device='localhost.localdomain' and component='zenhub' and eventKey='' and
(eventClass='/App/Stop' or eventClass='/App/Start'): --> 1
DEBUG:zen.Events:insert into log (evid, userName, text) select evid, "admin",
"auto cleared" from status where clearid = "7f0000013633da45ffffea8": --> 1
DEBUG:zen.Events:DELETE FROM status WHERE clearid IS NOT NULL: --> 1
DEBUG:zen.Events:insert into history set
firstTime=1198855877.207,severity=0,component='zenhub',summary='zenhub
started',dedupid='localhost.localdomain|zenhub|/App/Start||0|zenhub
started',eventKey='',device='localhost.localdomain',eventClass='/App/Start',lastTime=1198855877.207,message='zenhub
started',deletedTime=null,evid='7f0000013633da45ffffea8': --> 1
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
{comment} Now I am starting zenperfsnmp here {/comment}
DEBUG:zen.Events:EventClassInst=Start
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.Events:update status set clearid = '7f0000013633da50fffeea8' where
device='localhost.localdomain' and component='zenperfsnmp' and eventKey='' and
(eventClass='/App/Stop' or eventClass='/App/Start'): --> 1
DEBUG:zen.Events:insert into log (evid, userName, text) select evid, "admin",
"auto cleared" from status where clearid = "7f0000013633da50fffeea8": --> 1
DEBUG:zen.Events:DELETE FROM status WHERE clearid IS NOT NULL: --> 1
DEBUG:zen.Events:insert into history set
firstTime=1198855888.393,severity=0,component='zenperfsnmp',agent='zenperfsnmp',summary='started',dedupid='localhost.localdomain|zenperfsnmp|/App/Start||0|started',manager='localhost',eventKey='',device='localhost.localdomain',eventClass='/App/Start',lastTime=1198855888.393,message='started',deletedTime=null,evid='7f0000013633da50fffeea8':
--> 1
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
DEBUG:zen.Events:EventClassInst=Stop
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.Events:insert into status set
firstTime=1198855888.679,severity=2,component='zenperfsnmp',agent='zenperfsnmp',summary='stopped',dedupid='localhost.localdomain|zenperfsnmp|/App/Stop||2|stopped',manager='localhost',eventKey='',device='localhost.localdomain',eventClass='/App/Stop',lastTime=1198855888.679,message='stopped',evid='7f0000013633da50fffdea8'
on duplicate key update
summary='stopped',count=count+1,lastTime=1198855888.679: --> 1
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
WARNING:zenhub:removing listener
WARNING:zenhub:removing listener
Then here is the output from zenperfsnmp:
Code:
DEBUG:zen.zenperfsnmp:received config for rho
DEBUG:zen.thresholds:Updating threshold ('CPU Utilization', ('rho', ''))
DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('rho', 'eth0'))
DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('rho', 'lo'))
DEBUG:zen.thresholds:Updating threshold ('Free Space 90 Percent', ('rho', '/'))
DEBUG:zen.thresholds:Updating threshold ('Free Space 90 Percent', ('rho',
'/boot'))
DEBUG:zen.zenperfsnmp:run
DEBUG:zen.zenperfsnmp:Connecting to localhost
DEBUG:zen.zenperfsnmp:Logging in as admin
WARNING:zen.zenperfsnmp:Reconnected to ZenHub
DEBUG:zen.zenperfsnmp:setting up services EventService, SnmpPerfConfig
DEBUG:zen.zenperfsnmp:chaining getInitialServices with d2
DEBUG:zen.zenperfsnmp:callback after getting service EventService
DEBUG:zen.zenperfsnmp:callback after getting service SnmpPerfConfig
DEBUG:zen.zenperfsnmp:Calling connected.
DEBUG:zen.zenperfsnmp:connected
DEBUG:zen.zenperfsnmp:Sending event {'severity': 0, 'component': 'zenperfsnmp',
'agent': 'zenperfsnmp', 'summary': 'started', 'manager': 'localhost', 'device':
'localhost.localdomain', 'eventClass': '/App/Start'}
INFO:zen.zenperfsnmp:fetching property items
DEBUG:zen.zenperfsnmp:Updated configCycleInterval config to 360
INFO:zen.zenperfsnmp:getting threshold classes
DEBUG:zen.zenperfsnmp:Loading classes ['Products.ZenModel.MinMaxThreshold']
INFO:zen.zenperfsnmp:checking for outdated configs
INFO:zen.zenperfsnmp:fetching configs for []...
INFO:zen.zenperfsnmp:fetching default RRDCreateCommand
INFO:zen.zenperfsnmp:fetching snmp status
INFO:zen.zenperfsnmp:Initiating incremental device load
DEBUG:zen.zenperfsnmp:Fetching configs for 1 devices
DEBUG:zen.zenperfsnmp:Fetching config for ['rho']
DEBUG:zen.zenperfsnmp:getting device ping issues
DEBUG:zen.zenperfsnmp:received config for rho
DEBUG:zen.thresholds:Updating threshold ('CPU Utilization', ('rho', ''))
DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('rho', 'eth0'))
DEBUG:zen.thresholds:Updating threshold ('Utilization 75 perc', ('rho', 'lo'))
DEBUG:zen.thresholds:Updating threshold ('Free Space 90 Percent', ('rho', '/'))
DEBUG:zen.thresholds:Updating threshold ('Free Space 90 Percent', ('rho',
'/boot'))
DEBUG:zen.zenperfsnmp:Finished fetching configs for 1 devices
INFO:zen.zenperfsnmp:Configured 1 of 1 devices
DEBUG:zen.zenperfsnmp:unresponsive devices: [['rho', 1, 559]]
INFO:zen.zenperfsnmp:Count 0 good 0 bad 0 time 0.000064
INFO:zen.zenperfsnmp:sent 0 OID requests
INFO:zen.zenperfsnmp:collected 0 of 0 devices in 0.00
DEBUG:zen.zenperfsnmp:Sending event {'severity': 3, 'component': 'zenperfsnmp',
'agent': 'zenperfsnmp', 'summary': 'stopped', 'manager': 'localhost', 'device':
'localhost.localdomain', 'eventClass': '/App/Stop'}
DEBUG:zen.zenperfsnmp:removing service EventService
DEBUG:zen.zenperfsnmp:removing service SnmpPerfConfig
INFO:zen.zenperfsnmp:zenperfsnmp shutting down
Of course, I didn't pass in the "--cycle" parameter, so the zenperfsnmp appears
to have ended after one cycle time. Looking at the output between both zenhub
and zenperfsnmp, to the untrained eye nothing strikes me as funny. How about
you?
What would I try next if the daemons seem to work just fine run in the
foreground but not background?
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=14736#14736
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
