On Fri, 2005-10-14 at 15:25 +0200, Loic Domaigne wrote:
> monitor -u lodo -r 10 -o prNames -o prErrMessage "proc" prErrorFlag != 0
> monitor -u lodo -r 10 -o prNames -o prErrMessage "proc" prErrorFlag == 0
> My first surprise was to get the following message from snmpd:
>
> /export/home/lodo/etc/snmpd2.conf: line 92: Error: duplicate trigger name
>
> which corresponds to the second monitor.
That's correct.
You've got two different monitor settings:
prErrorFlag == 0
and
prErrorFlag != 0
both identified by the same index name ("proc").
I'm suprised the previous code didn't complain about this,
actually. Distinct monitor statements must have distinct names.
Try
monitor ..... "proc1" prErrorFlag != 0
monitor ..... "proc2" prErrorFlag == 0
instead.
Alternatively, the new implementation also supports the syntax
monitor ..... "proc" != prErrorFlag
to fire on *any* change in the monitored value.
This one entry ought to be equivalent to your previous two.
> I kill prg2 for instance, I checked that the entry
> UCD-SNMP-MIB::prErrorFlag.2 got the value 1 as expected.
> However no inform was sent out (checked with snoop).
Bother!
>
> Even worse, the following monitor:
> monitor -u lodo -i .... "proc" prErrorFlag.1 != 0
> isn't working anymore.
That's probably the same underlying problem.
> Let me know if I can further help.
OK - please try running the agent using:
snmpd -f -Le -Ddisman:event
let things settle down, and then kill off "prg2".
What debug output does the agent display?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.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
