Hello list,

Looking for tips on how to troubleshoot this:

    net-snmp ver 5.9.1

    $ snmpwalk -v2c <etc> localhost .1

    <elided>
    TCP-MIB::tcpInErrs.0 = Counter32: 0
    TCP-MIB::tcpOutRsts.0 = Counter32: 0
TCP-MIB::tcpConnectionState.ipv4."192.168.122.102".52680.ipv4."192.168.1.200".514 = INTEGER: established(5) TCP-MIB::tcpConnectionProcess.ipv4."192.168.122.102".52680.ipv4."192.168.1.200".514 = Gauge32: 1321
    TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".22 = Gauge32: 970
    TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".25 = Gauge32: 1250
    TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".111 = Gauge32: 951
    TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".8053 = Gauge32: 976
    TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".43677 = Gauge32: 956
    TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53 = Gauge32: 976
    TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53 = Gauge32: 976
    Error: OID not increasing: TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53
     >= TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53

Only have trouble with this one OID.

Restarting snmpd does not fix the problem. Rebooting almost
always "fixes" the problem. Happens on 2 different hosts,
one is running "on metal" (a busy hypervisor), one is a
virtual machine running on that hypervisor, with nearly
no activity.

Many hosts (>10) with identical snmp/snmpd configurations, so
I'm tempted to rule out config issues. There are only a tiny
number of TCP listeners on the broken host.

Right now, the virtual machine is experiencing the issue:

$ ssh slacky-0 netstat -ant | cat -n
     1  Active Internet connections (servers and established)
     2  Proto Recv-Q Send-Q Local Address           Foreign Address         State
     3  tcp        0      0 127.0.0.1:53 0.0.0.0:*               LISTEN
     4  tcp        0      0 127.0.0.1:53 0.0.0.0:*               LISTEN
     5  tcp        0      0 127.0.0.1:953 0.0.0.0:*               LISTEN
     6  tcp        0      0 127.0.0.1:953 0.0.0.0:*               LISTEN
     7  tcp        0      0 0.0.0.0:8053 0.0.0.0:*               LISTEN
     8  tcp        0      0 0.0.0.0:8053 0.0.0.0:*               LISTEN
     9  tcp        0      0 127.0.0.1:631 0.0.0.0:*               LISTEN
    10  tcp        0      0 0.0.0.0:111 0.0.0.0:*               LISTEN
    11  tcp        0      0 0.0.0.0:25 0.0.0.0:*               LISTEN
    12  tcp        0      0 0.0.0.0:22 0.0.0.0:*               LISTEN
    13  tcp        0      0 0.0.0.0:43677 0.0.0.0:*               LISTEN
    14  tcp        0      0 192.168.122.102:53 0.0.0.0:*               LISTEN     15  tcp        0      0 192.168.122.102:53 0.0.0.0:*               LISTEN     16  tcp        0      0 192.168.122.102:22 192.168.1.100:57602     ESTABLISHED     17  tcp        0      0 192.168.122.102:52680 192.168.1.200:514       ESTABLISHED
    18  tcp6       0      0 :::111 :::*                    LISTEN
    19  tcp6       0      0 :::22 :::*                    LISTEN
    20  tcp6       0      0 ::1:53 :::*                    LISTEN
    21  tcp6       0      0 ::1:53 :::*                    LISTEN
    22  tcp6       0      0 :::35313 :::*                    LISTEN
    23  tcp6       0      0 ::1:631 :::*                    LISTEN
    24  tcp6       0      0 fe80::5054:ff:fec3:9:53 :::*                    LISTEN     25  tcp6       0      0 fe80::5054:ff:fec3:9:53 :::*                    LISTEN

According to ps, the daemon was invoked with:
    /usr/sbin/snmpd -A -p /var/run/snmpd -a -c /etc/snmp/snmpd.conf

This host has lots of free memory and I see no evidence of a memory leak.

Suggestions for how to debug the daemon for this issue is appreciated,
pointers to docs especially.
--
Charles Polisher



_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to