--On Monday, March 07, 2005 5:56 PM +0100 Marko Riedel <[EMAIL PROTECTED]> wrote:
Hello there,
we upgraded to 1.1.0. So far everything seems to be okay, but traps no longer work. We did not change the code at the machines that send traps, except to install the latest version (1) of Mon::Client.
Now traps that used to work cause the following output:
trap trap 1 from grp=somegroup svc=DYNDNS, sta=255 failure for somegroup DYNDNS 1110213302 somehost DYNDNS OKA
As you can see the trap includes the output from the remote host, which says that everything is okay. We did not chage the return codes at all. How can a trap that used to work suddenly turn into a failure?
Thank you for your help.
Marko,
I'm trying to track this down to see if there is a bug. The output you included is the syslog message thats sent on a trap being received. The only problem I see in that message is that the source IP address of the trap isn't being filled in.
Are there any other log messages? And can you provide a bit more detail on the exact failure behavior you see? I assume that mon is just ignoring the trap completely. Does it just ignore certain traps, or all of them?
-David
David Nolan <*> [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
a herd of rogue emacs fsck your troff and vgrind your pathalias!_______________________________________________ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
