RE: snmpd stops responding after ~ 1000 snmpwalks

Hi, I ran my script in the debug mode. This is the stack. Any suggestion
would be greatly appreciated. THANKS!!!

Program received signal SIGINT, Interrupt.
[Switching to Thread 16384 (LWP 16285)]
0x402a4658 in sigsuspend () from /lib/libc.so.6

(gdb) bt
#0 0x402a4658 in sigsuspend () from /lib/libc.so.6
#1 0x406f5c58 in __pthread_wait_for_restart_signal ()
from /lib/libpthread.so.0
#2 0x406f1fcb in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0
#3 0x4036c0f6 in pthread_cond_wait@GLIBC_2.0 () from /lib/libc.so.6
#4 0x408ba0d4 in protocol::ProtocolClient::sendBatchWithIdAndWait() (
this=0x40b16e18) at ProtocolClient.cpp:160
#5 0x408b9bf6 in
protocol::ProtocolClient::sendObjectAndWait(protoc ol::Object const&)
(this=0x40b16e18, object=@0xbfffdce0) at ProtocolClient.cpp:118
#6 0x408b6b97 in ProtocolDataAccess::getAllPhysicalVolumes() const (
this=0xfffffffc) at ProtocolDataAccess.cpp:149
#7 0x408b4c4e in getPvData (pvData=0x40902de0, max_size=1000)
at sample.cpp:197
#8 0x408b4083 in physicalVolumeTable_get_first_data_point ()
from /usr/local/ibrix/lib/snmp/physicalVolumeTable.so
#9 0x400d4f97 in netsnmp_table_iterator_helper_handler (handler=0x80d43f8,
reginfo=0x80d4108, reqinfo=0x40b11f78, requests=0x40b10d38)
at table_iterator.c:448
#10 0x40027d19 in netsnmp_call_handler (next_handler=0x80d43f8,
reginfo=0x80d4108, reqinfo=0x40b11f78, requests=0x40b10d38)
at agent_handler.c:386
#11 0x40028d8c in netsnmp_call_next_handler (current=0x80d4428, reginfo=0x8,
reqinfo=0xbfffda58, requests=0xfffffffc) at agent_handler.c:469
---Type <return> to continue, or q <return> to quit---
#12 0x400d7fad in table_helper_handler (handler=0x80d4428,
reginfo=0x80d4108,
reqinfo=0x40b11f78, requests=0x40b10d38) at table.c:565
#13 0x40027d19 in netsnmp_call_handler (next_handler=0x80d4428,
reginfo=0x80d4108, reqinfo=0x40b11f78, requests=0x40b10d38)
at agent_handler.c:386
#14 0x40028d8c in netsnmp_call_next_handler (current=0x80d4450, reginfo=0x8,
reqinfo=0xbfffda58, requests=0xfffffffc) at agent_handler.c:469
#15 0x400cf279 in netsnmp_bulk_to_next_helper (handler=0xbfffda58,
reginfo=0xfffffffc, reqinfo=0x40b11f78, requests=0x40b10d38)
at bulk_to_next.c:85
#16 0x40027d19 in netsnmp_call_handler (next_handler=0x80d4450,
reginfo=0x80d4108, reqinfo=0x40b11f78, requests=0x40b10d38)
at agent_handler.c:386
#17 0x40027f57 in netsnmp_call_handlers (reginfo=0x80d4108,
reqinfo=0x40b11f78, requests=0x40b10d38) at agent_handler.c:449
#18 0x4001fdfe in handle_var_requests (asp=0x40b11a80) at snmp_agent.c:2248
#19 0x40020ee2 in handle_pdu (asp=0x40b11a80) at snmp_agent.c:3007
#20 0x40020b14 in netsnmp_handle_request (asp=0x40b11a80, status=1081049371)
at snmp_agent.c:2803
#21 0x4001ee4e in handle_snmp_packet (op=1, session=0x8, reqid=1432325434,
pdu=0x40b16660, magic=0xfffffffc) at snmp_agent.c:1659
#22 0x4010e154 in _sess_process_packet (sessp=0x80a29d0, sp=0x80d8fc0,
isp=0x80c87c8, transport=0x80a28a8, opaque=0x40b11d80, olength=16,
packetptr=0x40b00490 "01\002\001", length=51) at snmp_api.c:5127
#23 0x4010ee84 in _sess_read (sessp=0x80a29d0, fdset=0x80a28a8)
at snmp_api.c:5525
#24 0x4010f478 in snmp_sess_read (sessp=0x80a29d0, fdset=0xbfffe840)
at snmp_api.c:5544
#25 0x4010e486 in snmp_read (fdset=0xbfffe840) at snmp_api.c:5179
#26 0x0804b63d in receive () at snmpd.c:1151
#27 0x0804ac16 in main (argc=4, argv=0xbffffa14) at snmpd.c:985
#28 0x402918c7 in __libc_start_main () from /lib/libc.so.6
-----Original Message-----
From: net-snmp-coders-admin@lists.sourceforge.net
[mailto:net-snmp-coders-admin@lists.sourceforge.net] On Behalf Of Wes
Hardaker
Sent: Friday, February 11, 2005 11:20 AM
To: Alex Koifman
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpd stops responding after ~ 1000 snmpwalks

>>>>> On Thu, 10 Feb 2005 14:24:32 -0500, "Alex Koifman"
<akoifman@yahoo.com> said:

Alex> Running snmpwalk for my private MIB (using dynamic modules,
Alex> dlmod) for about 1000 times makes SNMP agent not respond. Each
Alex> walk is about 10 gets. I do not use dynamic memory allocation.
Alex> I repeated the test a few times. The same result. When the
Alex> agent stops responding I see no debug output.

You should run it in a debugger or attach a debugger to it and see
where it stops.

gdb -p PROCCESSID
....
gdb> where

where will show you where it's currently running.

--
Wes Hardaker
Sparta


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders