Description of problem: net-snmpd wasn't originally installed, after "up2date
net-snmp" and trying to start /etc/init.d/snmpd start I get the following error
Starting snmpd: /usr/sbin/snmpd: symbol lookup error:
/usr/lib/libnetsnmpmibs.so.5: undefined symbol: netsnmp_TCPIPv6Domain
it's possible that related package/library wasn't installed on this particular
systems, but there was no rpm dependancy problem.
Version-Release number of selected component (if applicable):
The problem appears only on two RHEL4 systems installed identically with limited
set of rpm packages, all other systems we have run snmpd without this problem.
Steps to Reproduce:
snmpd doesn't start
snmpd to start
Which version of net-snmp do you have? Are you running SELinux? Did you modified
snmpd.conf file? How?
net-snmp is the one distributed with RHEL4 - net-snmp-5.1.2-11.EL4.6
SELinux is configured in "permissive" mode
I did some changes, but I've tried with the standard snmpd.conf,
I also downloaded and recompiled net-snmp source rpm and it gives me the same
Do you have net-snmp-libs installed? rpm -q net-snmp-libs
net-snmp-libs is installed as well,
I am sorry nobody took care of this bug. I am new maintainer of net-snmp an I am
cleaning old bugs. Are you still able to reproduce the bug in latest RHEL 4.5
we only have have the problem on two of our RHEL 4 systems, it persists after
all recent RHEL4 updates, I've tried even to recompile snmp but the same result.
All our other installations properly start snmpd
We should reinstall with RHEL5, which I presume will fix the problem
I think you can close this Tt
BTW, there is another problem with the latest update of net-snmp 5.1.2 in RHEL4
the startup command is OPTIONS="-Lsd -Lf /dev/null -p /var/run/snmpd.pid -a"
and we'd like to suppress the logging of the snmp queries, so
the following doesn't work on RHEL4 but work on RHEL5: #OPTIONS="-Lf /dev/null -
p /var/run/snmpd -a -I -smux"
instead, with RHEL4 I had to use OPTIONS="-l /dev/null -p /var/run/snmpd.pid -
a -I -smux"
Thank you for the info. I am closing the bug.
Regarding your logging problem, I think it's already reported, see bug 241581.
It should be fixed in RHEL 4.6.