There will be several tests to be done. As far as i can tell today, it seems not to be an generell snmp problem.
Last week i spend by observing some of our servers wich die that way. And it seems that its an Problem of some OIDs or the interact with how fast they are asked. I found out that an hand written perl script kills our servers. This perl script does 5 to 6 asks to the server. We slowed it down by waiting 1 second each ask. And the server is still running. So it could be that snmpwalk just asks to much questions, which the server cant handle. 2010/1/14 Brendan P. Caulfield <[email protected]> > As far a I can tell this is still not fixed in Hardy. Obviously this > issue is now known as a patch has been released for Karmic. > Unfortunately, I don't have the luxury of upgrading all my servers and > rolling my own packages for this is something I would like to avoid. > Will this be fixed in Hardy (LTS)? I assume this would have been the > priority over Karmic, no? > > Thanks, > > -brendan > > -- > snmpd dies after requests with snmpwalk > https://bugs.launchpad.net/bugs/426813 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “net-snmp” package in Ubuntu: Fix Released > Status in “net-snmp” source package in Hardy: Triaged > > Bug description: > Hi, > > I'm using Ubuntu 8.04 (up-to-date) and have the service snmpd running on > it. The problem is, when I'm trying to snmpwalk the server (eg. in a while > - loop, every 5 seconds), then after max 5 minutes snmpd dies. The > package-version is 5.4.1~dfsg-4ubuntu4.2. > > /var/log/messages says: > ================== > ... kernel: [ 4167.266281] snmpd[6485] trap divide error rip:7f2ed9c32c2c > rsp:7fffe25cd3d0 error:0 > > I'm using snmpwalk as follows: > ======================= > snmpwalk -v2c -c test_server 162.23.61.160 > > My /etc/default/snmpd is: > ================== > # This file controls the activity of snmpd and snmptrapd > # MIB directories. /usr/share/snmp/mibs is the default, but > # including it here avoids some strange problems. > export MIBDIRS=/usr/share/snmp/mibs > # snmpd control (yes means start daemon). > SNMPDRUN=yes > # snmpd options (use syslog, close stdin/out/err). > SNMPDOPTS='-LS 0-4 d -Lf /dev/null -u snmp -p /var/run/snmpd.pid' > # snmptrapd control (yes means start daemon). As of net-snmp version > # 5.0, master agentx support must be enabled in snmpd before snmptrapd > # can be run. See snmpd.conf(5) for how to do this. > TRAPDRUN=no > # snmptrapd options (use syslog). > TRAPDOPTS='-Lsd -p /var/run/snmptrapd.pid' > # create symlink on Debian legacy location to official RFC path > SNMPDCOMPAT=yes > > My /etc/snmp/snmpd.conf: > ==================== > view all included .1 80 > view system included .iso.org.dod.internet.mgmt.mib-2.system > syslocation ServerRoot (configure /etc/snmp/snmpd.local.conf) > syscontact Root <r...@localhost> (configure /etc/snmp/snmpd.local.conf) > rocommunity public 127.0.0.1 > rocommunity test_server 192.168.44.0/23 > rocommunity test_server 162.23.61.0/24 > > On the client server, where I run a script, that repeats snmpwalk every 5 > seconds , the error occurs (if it occurs) always at the same place: > ======================================================================== > ... > HOST-RESOURCES-MIB::hrDeviceErrors.1028 = Counter32: 0 > HOST-RESOURCES-MIB::hrDeviceErrors.1029 = Counter32: 0 > HOST-RESOURCES-MIB::hrProcessorFrwID.768 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.769 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.770 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.771 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.772 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.773 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.774 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorFrwID.775 = OID: SNMPv2-SMI::zeroDotZero > HOST-RESOURCES-MIB::hrProcessorLoad.768 = INTEGER: 0 > HOST-RESOURCES-MIB::hrProcessorLoad.769 = INTEGER: 0 > Timeout: No Response from 162.23.61.160 > Timeout: No Response from 162.23.61.160 > Timeout: No Response from 162.23.61.160 > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/426813/+subscribe > -- snmpd dies after requests with snmpwalk https://bugs.launchpad.net/bugs/426813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
