Feb 25, 2010 4:40 PM
Zentrap will not restart, must reboot?
-
Like (0)
Zenoss v. 2.5.1 - everything works great unless I need to "zentrap restart" or "zenoss restart". Zentrap does start properly following a full reboot of the server, but will not restart if it is stopped anytime after bootup. I can't find any error messages explaining why. I've looked in /var/log/messages, /var/log/syslog, /$zenhome/log/*.log - nothing appears even slightly relevant.
Immediately after bootup, 'ps faux | grep snmp' shows the following:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
snmp 5398 0.0 0.0 49576 5100 ? S 08:48 0:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u snmp -I -smux -p /var/run/snmpd.pid -c /etc/snmp/snmpd.conf
and 'netstat -nlpa | grep snmp' shows:
udp 0 0 0.0.0.0:161 0.0.0.0:* 0 13547 5398/snmpd
unix 2 [ ] DGRAM 13372 5398/snmpd
Zentrap appears to be called this way during startup
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
zenoss 6079 0.1 0.6 162240 50188 ? S 08:49 0:01 /usr/local/zenoss/python/bin/.python.bin /usr/local/zenoss/zenoss/Products/ZenEvents/zentrap.py --configfile /usr/local/zenoss/zenoss/etc/zentrap.conf --cycle --daemon --useFileDescriptor=4
Any thoughts on how I can troubleshoot this?
Thanks
You already have something listening on the snmp trap port (162). Disable any SNMP services that you already have running on that server. I think what's happening is that Zenoss is starting before some other snmp related process and is grabbing that port first, but as soon as it lets go of the port, the other process grabs it.
It's really just a guess but it's the most common issue that I've seen to cause zentrap not to start.
I wondered about that... I forgot to include in my original post that I have tried killing snmpd and rerunning netstat to confirm everything is clear, but zentrap still refuses to start.
snmpd is started earlier in the bootup process than zenoss-stack. (S21snmpd, S80zenoss-stack) I tried moving snmpd to S81 but had even weirder results. Everything still started up properly after bootup, but later zentrap just died and would not restart.
I kind of figure this is probably as simple as I am looking for clues in the wrong place...or not understanding the clues in front of me? Should snmpd be completely disabled? (I haven't tried that yet...)
You may not see it with the grep string you were using.
~:/home/rmatte# netstat -nlpa | grep 162
udp 0 0 0.0.0.0:162 0.0.0.0:* 4733/.python.bin
Stop zentrap then try that command, see if something else grabs that port.
snmpd can be enabled, I have it enabled on my Zenoss servers. Just make sure that you don't have something like snmptrapd running.
Ahh, this conversation has sufficiently jarred my memory. I am also running a specialized snmp trap receiver that is supposed to only be listening on UDP 1162. Killing that server allows me to restart zentrap properly. Hmmm...
Thanks for the help. =)
No problem.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||