I have an old RHEL3 box on my network which I monitor via SNMP from my Ubuntu server running MRTG. I've been doing this for years with continually-updated versions of 32-bit Ubuntu, and have never had problems.
Over the long New Years weekend, I replaced my 32-bit 12.04 install with a fresh 64-bit 12.10 install. The SNMP & MRTG configs were copied from the 12.04 install (on a separate drive, so it's still accessible). Ever since then, I've been getting intermittent connectivity errors with SNMP to the RHEL server ("yavin"). MRTG polls every 5 minutes, and most of the time, it succeeds. It fails at variable intervals ranging from 10 minutes to 4 hours, but probably averaging one failure every 30 minutes. Here's the error message I'm emailed each time:
SNMP Error:
no response received
SNMPv1_Session (remote host: "yavin" [192.168.21.246].161)
community: "undisclosed"
request ID: 2110321503
PDU bufsize: 8000 bytes
timeout: 5s
retries: 5
backoff: 1)
at /usr/share/perl5/SNMP_util.pm line 492
SNMPGET Problem for ifInOctets.2 ifOutOctets.2 sysUptime sysName on undisclosed@yavin::::::v4only at /usr/bin/mrtg line 2339
2013-01-04 09:15:01: WARNING: skipping because at least the query for ifInOctets.2 on yavin did not succeed
2013-01-04 09:15:01: WARNING: no data for ifInOctets&ifOutOctets:undisclosed@yavin. Skipping further queries for Host yavin in this round.
2013-01-04 09:15:30: ERROR: Target[yavin-eth0][_IN_] ' $target->[28]{$mode} * 8' (warn): Use of uninitialized value in multiplication (*) at (eval 74) line 1.
2013-01-04 09:15:30: ERROR: Target[yavin-eth0][_OUT_] ' $target->[28]{$mode} * 8' (warn): Use of uninitialized value in multiplication (*) at (eval 75) line 1.
All further queries to yavin for that round of MRTG also fail. The SNMP line from MRTG is pretty straightforward, and works most of the time:
Target[yavin-eth0]: ifInOctets.2&ifOutOctets.2:undisclosed@yavin * 8
Logs on yavin don't show anything. /etc/snmp/snmp.conf on the Ubuntu box contains only comments. This worked 100% of the time before the Ubuntu 12.10 upgrade, so I don't believe it's a hardware problem.
Any ideas what's going on?
Bookmarks