please help with service dependencies

[James DeZego]

Using NRPE_NT running on a Windows server as a WMI Proxy to process
checks on Windows servers via WMI scripts. The initial problem was that
when the proxy was down, or rebooted, we got thousands of alerts from
the services that used the proxy to do checks. We thought that to fix
this we would make all the WMI checks dependent upon the NRPE service
running on the proxy. This way when the parent NRPE service was down or
unreachable, the WMI checks would not be processed. This is NOT working
to due the time it takes for the NRPE service to go from soft-down to
hard-down (during this time tons of alerts are sent out). We enabled
soft state dependency and this fixed the problem, but it will KILL our
WMI proxy as its now doing MANY more checks (the NRPE parent service is
constantly checked to get the current state as opposed to using the last
know state, which is what happens when soft state dependencies are
turned off)

 

So what is the answer to my problem? I need to make sure that when the
NRPE service running on the proxy is down or unreachable, ALL wmi checks
immediately stop and not even a single alert is sent out.

 

Thank you

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070313/7633aa97/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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