Latest from hardy-updates:
snmpget --version:
NET-SNMP version: 5.4.1
apt-cache show snmp:
Architecture: amd64
Source: net-snmp
Version: 5.4.1~dfsg-4ubuntu4.2
--
COUNTER64 broken in NetSNMP::agent
https://bugs.launchpad.net/bugs/406171
You received this bug notification because you are a
** Changed in: net-snmp (Ubuntu)
Status: Incomplete = New
--
COUNTER64 broken in NetSNMP::agent
https://bugs.launchpad.net/bugs/406171
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in ubuntu.
--
Ubuntu-server-bugs
I didn't have any when I initially wrote this but I was writing an
embedded agent for testing special behaviours in Nagios-plugins's
check_snmp.
The easiest way to test is to take the latest nagios-plugins snapshot from
http://repo.or.cz/w/nagiosplugins.git (there is a snapshot download link
Public bug reported:
Trying to use COUNTER64 in NetSNMP::agent doesn't work. This is a long-
standing bug that has been fixed in SVN for 5.2.x, 5.3.x, 5.4.x and
trunk last year.
I noticed this bug a while ago (it was already reported to net-snmp) and
worked around it by using normal counters.
** Attachment added: Patch from SVN for 5.4.x branch.
http://launchpadlibrarian.net/29652830/perl-agent_COUNTER64.patch
--
COUNTER64 broken in NetSNMP::agent
https://bugs.launchpad.net/bugs/406171
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Marking Invalid because:
1. No thresholds were specified - specifying some kind of thresholds would
actually cause it to monitor properly.
2. Check_ntp is deprecated and both replacement plugins, check_ntp_peer and
check_ntp_time, should not show this weird behaviour.
** Changed in:
This was a feature since check_ntp had multiple possible possible
thresholds (-w/-c, -j/-k). Without any threshold specified it was not
checking anything besides receiving a response.
check_ntp_* does return critical on these cases and check_ntp is
deprecated and its behavior will not change.
--
