We've run into a classical deadlock situation:
An agentx subagent tries to send a reply message to the snmpd agent, but
its socket is full, so it hangs in send(). The snmpd has timed out and
is trying to resend the request. The socket in this direction is full,
too. Apparently the situation has occurred because the subagent has been
busy without responding to snmpd request which have come in in quite
great numbers.
So now both, snmpd and our subagent, are both waiting in send/sendto()
without being able to read from their side of the socket.
This may be a very rare situation, but it seems that it is not impossible.
Is there an official way to resolve this situation?
Josef
--
These are my personal views and not those of Fujitsu Technology Solutions!
Josef Möllers (Pinguinpfleger bei FTS)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://de.ts.fujitsu.com/imprint.html
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
