amavis-user March 2012 archive
Main Archive Page > Month Archives  > amavis-user archives
amavis-user: Re: amavisd-new-snmp problem

Re: amavisd-new-snmp problem

From: Mark Martinec <Mark.Martinec+amavis_at_nospam>
Date: Sat Mar 17 2012 - 00:57:27 GMT
To: amavis-users@amavis.org

Levi,

> I use net-snmp-5.3.2.2-17.el5 and amavisd-new / -snmp 2.7.0 on Centos 5.8
>
> I started the amavisd daemon and with 0 messages sent get:
>
> # snmpwalk -c public -v2c 127.0.0.1 AMAVIS-MIB::inMsgsSize
> SNMPv2-SMI::enterprises.15312.2.1.1.3.1.0 = Counter64: 2340844
>
> Now, after 1 message (only text with one word) sent:
>
> # snmpwalk -c public -v2c 127.0.0.1 AMAVIS-MIB::inMsgs
> SNMPv2-SMI::enterprises.15312.2.1.1.2.1.0 = Counter32: 1
> # snmpwalk -c public -v2c 127.0.0.1 AMAVIS-MIB::inMsgsSize
> SNMPv2-SMI::enterprises.15312.2.1.1.3.1.0 = Counter64: 6798935570412
> [...]
> I think it's problem with Counter64 counters. Can somebody tell me how
> to get correct values from message size counters over SNMP?

Indeed, it's a bug in net-snmp regarding 64-bit counters,
or rather, in its AgentX perl interface.

This is from amavisd-new 2.6.4 release notes:

  The setup was tested with Net-SNMP versions 5.3.2.3, 5.4.2.1 and 5.2.0.
  If you experience wild numbers served in Counter64 variables on a 64-bit
  platform, the following patch (at the server side) solves the problem:

    http://www.mail-archive.com/net-snmp-users@lists.sourceforge.net/msg19502.html

  The patch seems to already be incorporated into version 5.3.3 of Net-SNMP,
  and into 5.5 (but not in 5.4.2, nor in 5.2.0).

I don't have more recent information unfortunately.
Updated information on this bug resolution is welcome.

  Mark