Setting ping timeout and running on other machines didn't help either. --- Salsa <[EMAIL PROTECTED]> wrote:
> > --- Dave Shield <[EMAIL PROTECTED]> wrote: > > > On Wed, 2005-05-25 at 13:29, Salsa wrote: > > > > Dave> Is the master agent receiving SNMP requests > > Dave> from other management tools? > > > > Salsa> I don't think so. My subagent only sends > > traps. > > Salsa> Nothing more. It is not responsible for any > > Salsa> requests, > > > > Fair enough - I'm just trying to rule out as much > as > > possible. > > > > Salsa> I run snmpd, snmptrapd and subagent on the > > Salsa> same machine > > > > It might be worth running the "snmptrapd" on a > > separate host, so that it's not trying to act as > > an AgentX subagent. > > (There may be a simpler way to achieve this, > > I'm not sure). > > > > That probably won't make any difference, but it's > > worth clearing this out of the way too. > > > > By the same token, I'd be tempted to turn off the > > subagent "ping". You *might* be able to do this > > using > > agentxPingInterval 0 > > > > in the subagent's config file, but it's probably > > safer to edit the file 'agentx/subagent.c' and > > change '15' to '0' in subagent_pre_init(). Then > > recompile and reinstall both master and subagent. > > > > Again, that's *probably* not relevant, but Just > > In Case... > > > > > > > > 2005-05-25 09:16:46 agentx/master: send > > response, > > > > stat 0 (req=0x5d120d88,trans=0x0,sess=0x7) > > > > > > > 2005-05-25 09:16:46 agentx_build: packet built > > okay > > > > > > > > 2005-05-25 09:16:46 agentx/master: handle pdu > > > > (req=0x5d120d89,trans=0x0,sess=0x7) > > > > > > > > > > > 2005-05-25 09:16:46 agentx/master: send > > response, > > > > stat 0 (req=0x5d120d89,trans=0x0,sess=0x7) > > > > > > > 2005-05-25 09:16:46 agentx_build: packet built > > okay > > > > > > > > 2005-05-25 09:16:46 agentx/master: FAILED 104 > > -12 > > > > Failure in sendto (Connection reset by peer) > > > > > > > > > > > So the first sign of a problem is that the master > > agent can't send a response back to the subagent. > > > > But the subagent is still trying to send stuff to > > the master agent: > > > > 2005-05-25 09:16:46 agentx/master: handle pdu > > > > (req=0x5d120d8a,trans=0x0,sess=0x7) > > > > > > > > > > > 2005-05-25 09:16:46 agentx/master: send > > response, > > > > stat 0 (req=0x5d120d8a,trans=0x0,sess=0x7) > > > > > > > 2005-05-25 09:16:46 agentx_build: packet built > > okay > > > > > > > > 2005-05-25 09:16:46 agentx/master: FAILED 32 > -12 > > > > Failure in sendto (Broken pipe) > > > > and things get totally confused! > > > > > > > > I think the FAILED - 104 is when I kill my > > subagent > > > > Err... now I'm confused. > > I thought you said it was the master agent that > got > > killed, not the subagent. That's certainly the > > subject > > of this thread. > > > Well, first time (times actually) this happened, > my > subagent would freeze and I would kill it. So I > checked what was wrong and snmpd was not running, so > I > assumed my subagent was killing it. Now I realize > that > no one really dies. Actually it looks like my > subagent > provoked a deadlock with master agentx. So it is > there > waiting to send the final traps while master agent x > is there waiting for something and not responding > anyone. And they go like that forever. snmptrapd > cannot reconnect until I kill my subagent. After > that > snmptrapd is able to connect to master agentx again > and master agentx debug starts spitting those FAILED > lines beggining with one FAILED - 104 and then a lot > of FAILED - 32 (with broken pipes). snmptrapd also > displays some more traps after I kill my subagent. > > I said (at least tried to) earlier but I think I > was > not clear enough. And perhaps not enough now too, > but > I 'm clueless about what matters and what doesn't. > And > I'm giving symptons like: "All I know is that it > hurts > inside my belly." > > > > > Dave > > > > -- > Salsa > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > > ------------------------------------------------------- > SF.Net email is sponsored by: GoToMeeting - the > easiest way to collaborate > online with coworkers and clients while avoiding the > high cost of travel and > communications. There is no equipment to buy and you > can meet as often as > you want. Try it > free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click > _______________________________________________ > 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 > -- Salsa __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate online with coworkers and clients while avoiding the high cost of travel and communications. There is no equipment to buy and you can meet as often as you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click _______________________________________________ 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
