On 24/04/07, Pamidipati Suresh-G20238 <[EMAIL PROTECTED]> wrote: > Subagent was busy responding to snmpwalk (which comes as getnext > requests) till timestamp of Apr 5 18.36.56.098. SNMPD stopped responding > from timestamp Apr 5 18:36:57 for all the mib objects (owned by itself > and subagent).
The subagent isn't generating traps, then? Most of the AgentX hangup problems we've had reported seem to have been related to heavy trap generation - presumably triggering a race condition with traps vs incoming requests. > However, SNMPD was responding to subagent ping requests. > The ping interval was configured as 1 second. I'm wondering whether this might not be effectively the same problem in a new guise - with ping requests taking the place of traps. Was this a one-off problem, or can you reproduce it fairly reliably? If it's reproducible, then try reducing the frequency of your ping requests (or turn them off altogether). Does that make any difference? Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
