On Tue, 07 Sep 2004 12:21:04 -0400 Allan wrote: AM> I came accross an issue last week and I am starting to think it is a AM> problem somewhere within the exstensible/mteTriggerTable code. After, AM> snmpd detects a non zero boolean return status from extResult and sends AM> traps, it no longer evaluates beyond extResult.1 or prErrorFlag.1 once AM> the initial process is restored. Therefore, if there is a problem with AM> say extResult.4 a trap is never send to notify of a problem.
After some debugging with Allan in irc, it appears that the problem is that mteTriggerTable does not recover well from a timeout. Thus extensible scripts that complete and return within the default timeout work fine, but those that take longer will cause failures at various times, depending on how many ext entries there are, which ones take too long, and the caching of ext results. A timeout parameter to the monitor entry might help. The mteTriggerTable and exec tables should also be re-hauled to delegate requests, so they don't block the agent while processing. If the mteTriggerTable is monitoring 5 ext entries that take 5 seconds to complete, at 60 second intervals, agent availability would be seriously affected! -- 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-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
