Thanks for the "patch" but I compared and it's the same. The snmpd.c file is under the path of
/usr/local/src/net-snmp-5.2.pre1/agent/snmpd.c So... I didn't make any changes and used -Dsnmpd to run it. And... The most of the first 30 mins was like this snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 Then all of sudden, I got this snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 0 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 1 Connection from 127.0.0.1 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = 1 Connection from 127.0.0.1 snmpd/select: select( numfds=10, ..., tvp=0xbfffea58) snmpd/select: returned, count = -1 select: Invalid argument snmpd/main: sending shutdown trap snmpd/main: Bye... To me, it looks like it could not make a connection to 127.0.0.1 so snmpd shut down, yes? Thanks, - Tony Sutton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Story (Users) Sent: 12 October 2004 17:16 To: Tony Sutton Cc: [EMAIL PROTECTED] Subject: Re: snmpd problem On Fri, 8 Oct 2004 21:06:16 +0100 Tony wrote: TS> I don't know of any sub-agents, just snmpd itself. TS> TS> Is there anything I can look to see if there is any sub-agents running? You would have seen a bunch of "agentx" debug messages in the debug output you captured. Try applying this patch, and then running again, this time changing "-D" to "-Dsnmpd". It will produce a lot less output, and tell us what the error was for select. --- ../clean-5.1.x/agent/snmpd.c 2004-10-06 00:42:31.000000000 -0400 +++ agent/snmpd.c 2004-10-06 17:02:55.000000000 -0400 @@ -1193,6 +1185,7 @@ snmp_timeout(); break; case -1: + DEBUGMSGTL(("snmpd/select", " errno = %d\n", errno)); if (errno == EINTR) { /* * likely that we got a signal. Check our special signal -- Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
