Red Hat Bugzilla – Bug 128656
net-snmp doesn't completely start on boot
Last modified: 2007-11-30 17:07:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8
Description of problem:
I have a number of enterprise v3 installs, all with a simple /etc/snmpd/snmpd.conf file that just has 1-3 'rocommunity' statements in it. ie:
rocommunity public 192.168.0.10
rocommunity public 192.168.0.11
rocommunity public 192.168.0.12
Whenever I reboot the machines, the snmpd process does start but it doesn't respond to valid requests. I have to issue a 'service restart' and then everything works as expected.
I would expect this to work from 192.168.0.10:
`snmpwalk -v1 -c public rebootedserver`
but I get:
"Timeout: No Response from mysql2.db.gospelcom.net"
Once I restart snmpd, the snmpwalk works as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a simple config just like the one shown in the bug description
Actual Results: snmpd starts, but doesn't respond to queries
Expected Results: snmpd should respond to queries
after restarting snmpd, everything works as expected
May I have your complete snmpd.conf file?
That really is all of it. Here's an snmpd.conf that just exhibited
the same behavior, with communities and hosts/ips changed:
rocommunity foo host.domain.com
rocommunity foo host2.domain2.net
rocommunity foo 220.127.116.11
rocommunity foo 18.104.22.168
I didn't manage to reproduce it here even with the given conf file.
Snmpd correctly starts on boot. After boot if you run `service snmpd
status` do you see that the process is running?
This hasn't happened for me in several months. I think one of the updates may
have somehow taken care of it?