service event handler not called on "OK" event

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Thomas Hager
> Sent: Wednesday, May 23, 2007 8:29 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] service event handler not called on "OK" event
> 
> hi,
> 
> i'm testing event handlers on my nagios box (running 2.9) and ran into
> the following problem today:
> 

> well, that's where i'm stuck. all CRITICAL events are logged and
> executed, but the OK event is just logged, not executed.
> 
> any hints?

Based on what you've shown, it should be working. I can 100% confirm
that it does work with nagios-2.7. The following is from my own log,
similar to your muh.log --

Wed May 23 01:59:43 CDT 2007 .  winbind service check (CRITICAL) (SOFT)
(1) (<redacted>)... 
Wed May 23 02:04:52 CDT 2007 .  winbind service check (CRITICAL) (SOFT)
(1) (<redacted>)... 
Wed May 23 02:06:51 CDT 2007 .  winbind service check (CRITICAL) (SOFT)
(2) (<redacted>)... 
Wed May 23 02:06:51 CDT 2007 .  Restarting winbind service (2nd soft
critical state) on <redacted>... 
Shutting down Winbind services: [FAILED]
Starting Winbind services: [  OK  ]
Wed May 23 02:08:51 CDT 2007 .  winbind service check (OK) (SOFT) (3)
(<redacted>)...

Perhaps someone else can confirm that it's really borked in 2.9 or maybe
you could try downgrading to 2.7 to see if it works.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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