Description of problem:
manual invocation of "/etc/init.d/snmpd start" results in messages
claiming successful start in both /var/log/messages and
/var/log/boot.log, but a "ps ax" moments later shows no trace of the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install net-snmpd
2. /etc/init.d/snmpd start
3. ps ax | grep snmp
snmpd process has exited
snmpd process listening for requests
after debugging this for a while, it seems to choke on reading
/usr/share/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt, but without any
using strace, it gets a SIGSEGV shortly after "init_usm(): snmpusm.c,
2661:", then registering callbacks, and the last act is
"read_premib_configs(): read_config.c, 814:".
The reference above to SNMP-VIEW-BASED-ACM-MIB is probably spurious,
but I can't tell for sure.
Forgot to add: the last call to open() is:
open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 9
Just to prove my thoughts, do you have SELinux turned on?
SELinux is in "warn" mode.
This is really strange, I've tested net-snmp on fresh RHEL-4AS machine
(i386) with SELinux in Permissive mode and it works fine. Starting it
as a service, quering all values, nothing causes a crash. I've even
tried removing the proposed file if this would cause an error but
still no luck. May I also have you snmpd.conf file, do you have there
something specific? On which architecture are you running the snmp
its lm sensors - unloading the lm_sensors kernel modules fixes this. See bug 151040
Created attachment 112805 [details]
stdout/stderr with -Dall
Created attachment 112806 [details]
snmpd core file (5.1.2-11 x86)
Comment #6 is correct. Removing the eeprom and i2c_* modules enables proper
startup. Attachments (comments 7 & 8) show the failure mode.
Fix is ready, will come out with new update
*** Bug 161492 has been marked as a duplicate of this bug. ***
I didn't see this get pushed out with the 4U1 update; is net-snmp going to be
updated b/c of this issue?
The update fixing this issue is scheduled for U2.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.