Package: munin Version: 1.4.5-3 Severity: normal Tags: upstream This bug was originally reported in Ubuntu here:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/851625 and forwarded to upstream here: http://munin-monitoring.org/ticket/1143 I am reporting it here in Debian as well so that Debian users who experience this issue will know its status upstream. Including the full bug description: --- The plugin actually supports 32 bit counter as well as 64 bit counter. However, if the snmp server you are connecting to does not support 64 bit byte counters, snmp__if fails. When I tried to the snmp server which supports only 32 bit counter, the plugin returned as follows: #munin-run snmp_hostname_if_1 recv.value noSuchObject send.value noSuchObject Here is an example of problems I found in the code. # from line 244 if (defined ($response = $session->get_single($ifEntryIn64Octets) || $session->get_single($ifEntryInOctets))) { print "recv.value ", $response, "\n"; } In these lines, "$session->get_single($ifEntryIn64Octets" is supposed to return undefined value if the server doesn't support 64 bit counter. However, it actually returns "noSuchObject". So, these lines should be fixed like this: if (defined($response = $session->get_single($ifEntryIn64Octets))){ if ($response eq 'noSuchObject'){ # 64 bit counter is not supported $response = $session->get_single($ifEntryInOctets); } } else { # No response $response = 'U'; } print "recv.value ", $response, "\n"; # The information about my environment Description: Ubuntu 10.04.3 LTS Release: 10.04 munin-node: Installed: 1.4.4-1ubuntu1 Candidate: 1.4.4-1ubuntu1 Version table: *** 1.4.4-1ubuntu1 0 -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-17-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
