Trouble with Global event handlers in Nag 3 (b7). [SEC=UNCLASSIFIED]

Stanley.Hopcroft at Dest.gov.au Stanley.Hopcroft at Dest.gov.au
Sat Jan 5 08:46:40 CET 2008


Dear Folks,

I am writing to ask for help with global event handlers in Nagios 3.0
(b7).

The handler that worked Ok with Nag 2.9 seems to work erratically (ie
only some of the time; more often than not it doesn't do anything) with
3.0.

Nag would log (in nagios.log) this message with 2.9

[1186030923] GLOBAL HOST EVENT HANDLER:
Wollongong;DOWN;HARD;10;global_host_event_handler
[1186031313] GLOBAL HOST EVENT HANDLER:
Wollongong;UP;HARD;1;global_host_event_handler

but with 3.0b7 these,

[1199420252] GLOBAL HOST EVENT HANDLER:
Sydney-backup;(null);(null);(null);global_host_event_handler
[1199423092] GLOBAL HOST EVENT HANDLER:
Sydney-backup;(null);(null);(null);global_host_event_handler

but the definition of the handler command has not changed,

        command_name    global_host_event_handler
        command_line    $USER2$/global_host_event_handler $HOSTNAME$
$HOSTSTATE$ $HOSTSTATETYPE$ $LASTHOSTUP$ $LASTHOSTDOWN$
$LASTHOSTUNREACHABLE$ $HOSTDOWNTIME$

It is wonderful to see that the 3.x series has debug level, and type in
nagios.cfg, but I can't see what is useful with this problem. 

I think the event broker should be what I want even though I have no
event broker module in use.
When I try it I see a lot of messages about callbacks (which I didn't
know I had).

Any advice will be very welcome. Please point me to the FM if this is a
change from 2.x that I haven't noticed.

Thank you,

Yours sincerely.








Classification: UNCLASSIFIED

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list