On Wed, 7 Sep 2016 14:07:42 -0400 Sam wrote:
ST> Any ideas on how to resolve this? The problem seems to be
ST> in "transitioning" from one mib to the next.
ST>
ST> On Mon, Jan 25, 2016 at 4:32 PM, Sam Tannous <stann...@users.sf.net> wrote:
ST>
ST> > ------------------------------
ST> >
ST> > * [bugs:#2693] <http://sourceforge.net/p/net-snmp/bugs/2693/> snmpwalk
ST> > causes snmpd hang and CPU spike*
ST> >
ST> > On latest debian (Jessie, snmpd 5.7.2.1, also seen on 5.7.3) we noticed a
ST> > nasty bug where the snmpd
ST> > CPU spikes (to around 100%) and snmpd becomes completely unresponsive.
ST> > Only way to recover is a restart.
ST> >
ST> > The problem appears to be in the transition (snmpwalk) from .1.3.6.1.2.1.3
ST> > to .1.3.6.1.2.1.4
ST> >
ST> > The bug occurs only when we have "-V systemonly" on our community string
ST> >
ST> > rocommunity public default -V systemonly
ST> >
ST> > *and* we expose these tables:
ST> >
ST> > view systemonly included .1.3.6.1.2.1.1
ST> > view systemonly included .1.3.6.1.2.1.2
ST> > view systemonly included .1.3.6.1.2.1.3
ST> > view systemonly included .1.3.6.1.2.1.4.24
ST> >
ST> > (Adding a view for .1.3.6.1.2.1.4.1 fixes this problem!)
ST> >
ST> > The output we see before the freeze is this:
ST> >
ST> > root@jessie-1:/home/stannous# snmpwalk -v2c -cpublic localhost .1
ST> > ...
ST> > <output snipped>
ST> > ...
ST> > SNMPv2-SMI::mib-2.3.1.1.3.2.1.10.50.10.23 = IpAddress: 10.50.10.23
ST> > Timeout: No Response from localhost
Does increasing the timeout help any? e.g.
snmpgetnext -v2c -cpublic -r 0 -t 300 localhost \
SNMPv2-SMI::mib-2.3.1.1.3.2.1.10.50.10.23
How big is the forwarding file?
cat /proc/sys/net/ipv4/conf/all/forwarding | wc -l
Any log messages in the log while it's spinning its wheels?
\
--
Robert
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
