FW: I can't get my event handler to fire!

Brian A. Seklecki lavalamp at spiritual-machines.org
Fri Feb 22 16:25:23 CET 2008


Nagios doesn't check exec() error code results on event handlers.
non-zero return codes should be logged as critical errors.  

It's a known bug.  I reported it a while ago.

~BAS

On Wed, 2008-02-20 at 13:21 -0500, D'Ausilio, John wrote:
> Searching the archives I found where to look in debug .. it appears that
> Nagios thinks it's running my event handler. Macro expansion looks fine.
> Problem is .. it's not actually running it! Still lost ...
> 
> -----Original Message-----
> From: D'Ausilio, John 
> Sent: Wednesday, February 20, 2008 11:45 AM
> To: 'Marc Powell'; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] I can't get my event handler to fire!
> 
> Well, I added event_handler_enabled configuration and still I'm not
> getting my event handler fired. I've tried both for the service (PING)
> and for the host, individually and in combination. I don't see anything
> in the debug logs that would indicate that an event handler should have
> fired (even with the filter set to -1). The script is executable by the
> nagios user (logged in as that user, execute same commandline as in
> command def, no problem).
> 
> 1. What/where should I be able to see in terms of event handlers firing
> in the logs?
> 
> 2. Are event handlers affected by notification settings (I'm assuming
> not)?
> 
> 3. What the heck am I doing wrong? This looks like it should be
> straightforward!
> 
> john d
> 
> 
> >But not in the service{} definition unless it's referenced in the
> >template. In addition to the program-wide setting, it must also be
> >specifically enabled on a per-service basis.
> 
> 
> ######################################################################
> The information contained in this communication is confidential and
> may contain information that is privileged or exempt from disclosure
> under applicable law. If you are not a named addressee, please notify
> the sender immediately and delete this email from your system.
> If you have received this communication, and are not a named
> recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited.
> ######################################################################
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> 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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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