Hello all,
I recently started seeing these messages on the consoles of three production Centos 5.2 servers. They have been occurring nonstop for the past few days and show up routinely every five minutes.
INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes
Despite trying to debug this and googling for the last couple of hours, I haven't had any luck as to why the errors are generated or how to fix them. There are a ton of posts on the web related to other Id's, such as various tty ports and "x", but I haven't seen a single thing related to "snmp". The answer usually seems to be that there are misconfigured lines in /etc/inittab, but in my case there is nothing even remotely related to "Id snmp" in inittab.
The make matters more confusing, snmp isn't installed or being used on these machines. I doubled checked and the extent of any snmp packages are these two:
# rpm -qa | grep -i snmp perl-Net-SNMP-5.2.0-1.2.el5.rf net-snmp-libs-5.3.1-24.el5_2.1
Both only contain a couple of libraries, so I hardly believe they have anything to do with it.
According to what I've learned, this error is usually generated when init tries to continually respawn a process that dies immediately... but as to what process it could possible be I have no idea. I even tried to strace init (-p1), but apparently this is a forbidden operation:
# strace -p1 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
That's a shame too, but at least I could see what init is trying to do.
Any ideas? I'm just about stumped as to how to proceed at this point.
Thanks in advance.
Hi,
On Tue, Feb 10, 2009 at 14:23, David Halik dhalik@jla.rutgers.edu wrote:
INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes
What does "grep -i snmp /etc/inittab" say?
If there is really nothing, try "init q" to see if init is still using old contents of that file. If that does not help, try "init u" as well.
If it still does not fix it, please post the full contents of your inittab so that we can help you fix the problem.
HTH, Filipe
Thanks for the reply. I've tried both "init q" and "init u" without any luck, the message still appeared five minutes later. Init did post a message that it was reloaded, so the command worked, yet the process is still complaining about this "snmp" id.
Here's my inittab. It's fairly standard and I don't think any custom changes were made.
# # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, miquels@drinkel.nl.mugnet.org # Modified for RHS Linux by Marc Ewing and Donnie Barnes #
# Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault:
# System initialization. si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6
# Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5 x:5:respawn:/etc/X11/prefdm -nodaemon
Filipe Brandenburger wrote:
Hi,
On Tue, Feb 10, 2009 at 14:23, David Halik dhalik@jla.rutgers.edu wrote:
INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes
What does "grep -i snmp /etc/inittab" say?
If there is really nothing, try "init q" to see if init is still using old contents of that file. If that does not help, try "init u" as well.
If it still does not fix it, please post the full contents of your inittab so that we can help you fix the problem.
HTH, Filipe _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I finally had a eureka moment this morning and figured out the issues. Our Centos 5 servers are all running on Sun x4100 hardware which has a service processor that runs a firmware Debian install. Since the console for the Centos 5 server is effectively the same console as the service processor, what we were really seeing was the service processor init complaining. Once I figured that out it was easy enough to confirm.
Thanks for your time.
David Halik wrote:
Thanks for the reply. I've tried both "init q" and "init u" without any luck, the message still appeared five minutes later. Init did post a message that it was reloaded, so the command worked, yet the process is still complaining about this "snmp" id.
Here's my inittab. It's fairly standard and I don't think any custom changes were made.
# # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, miquels@drinkel.nl.mugnet.org # Modified for RHS Linux by Marc Ewing and Donnie Barnes #
# Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault:
# System initialization. si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6
# Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
# If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
# Run gettys in standard runlevels co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5 x:5:respawn:/etc/X11/prefdm -nodaemon
Filipe Brandenburger wrote:
Hi,
On Tue, Feb 10, 2009 at 14:23, David Halik dhalik@jla.rutgers.edu wrote:
INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes
What does "grep -i snmp /etc/inittab" say?
If there is really nothing, try "init q" to see if init is still using old contents of that file. If that does not help, try "init u" as well.
If it still does not fix it, please post the full contents of your inittab so that we can help you fix the problem.
HTH, Filipe _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos