Passive service on Windows 2003 box notifies intermittently

[C. Bensend]

> Nov 19 08:20:12 hostname nagios: SERVICE ALERT: winhost;System
> EventLog;CRITICAL;HARD;1;System [info] [USER32 #1074]: The process
> svchost.exe has initiated the restart of computer WINHOST on behalf of
> user NT AUTHORITY\SYSTEM for the following reason: No title for this
> reason could be found  Reason Code: 0x80070020  Shutdown Type: restart
>
> -- OK, Nagios generates a service alert here.  Yay.  But ...
>
> Nov 19 08:20:12 hostname nagios: PASSIVE SERVICE CHECK: winhost;System
> EventLog;2;System [info] [USER32 #1074]: The process Explorer.EXE has
> initiated the restart of computer WINHOST on behalf of user DOMAIN\me for
> the following reason: Application: Maintenance (Planned)  Reason Code:
> 0x84040001  Shutdown Type: restart  Commen
>
>
>    That's it.  No notification.  No nothing else, and I didn't skip
> any log entries other than one of the NSClient++ services getting a
> connection refused while the host was rebooting.
>
>    And what makes this worse is that it's not consistent - I get the
> entries from NSCA every time, but I only get the notifications SOME
> of the time.  Here is one that *did* work:

And a further data point...  Setting 'is_volatile' to 1 in the
service does *NOT* cause it to notify either.  :/

Help?

Benny


-- 
"It's not all about getting up and putting four slices of kickass
in a two slice toaster."         -- ark86, on Fazed.net



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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