Your message dated Mon, 5 Jun 2006 22:31:05 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Querying for HOST-RESOURCES-MIB::hrStorageAllocationFailures.2
causes snmpd to use max CPU
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: snmpd
Version: 5.1.2-6.2
Severity: grave
Justification: renders package unusable
Querying snmpd for HOST-RESOURCES-MIB::hrStorageAllocationFailures.2
causes snmpd to just spinlock. It consumes 100% CPU time and becomes
unavailable.
This appears to be the same issue as at
http://sourceforge.net/tracker/index.php?func=detail&aid=986238&group_id=12694&atid=112694
and that patch appears to be applied, but the bug is still occurring.
To reproduce:
apt-get install snmpd snmp
- Modify /etc/snmp/snmpd.conf, comment out line 61, uncomment line 62 to
enable a sec.name readonly with a community string of public
(obviously don't do this to an exposed box)
/etc/init.d/snmpd restart
snmpget -c public -v 1 localhost .1.3.6.1.2.1.25.2.3.1.7.2
That will set the daemon into a spin-lock (strace says its constantly
opening /etc/mtab).
-- System Information:
Debian Release: 3.0
Architecture: i386 (i686)
Kernel: Linux 2.4.24-grsec
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages snmpd depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libsensors3 1:2.9.1-1sarge3 library to read temperature/voltag
ii libsnmp5 5.1.2-6.2 NET SNMP (Simple Network Managemen
ii libwrap0 7.6-9 Wietse Venema's TCP wrappers libra
--- End Message ---
--- Begin Message ---
On Mon, Jun 05, 2006 at 01:31:49PM -0700, [EMAIL PROTECTED] wrote:
> Well, the OID doesn't seem to be present any more - I suppose its a fix
> since all I was concerned about was SolarWinds crashing our snmpd daemons.
Thanks -- in that case I'm closing it. :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
