-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/09 10:43 AM, Sergio Ariel wrote: > I have some services (in different hosts) I check by Nagios. > Some of these service checks spend some seconds to execute, so, I've set > a window time according each time execution. For example: I've some 30 > seconds timeout service check. > My problem is that when these host are DOWN, Nagios wait 30 seconds > trying to execute the service check. After this 30 seconds, then tell me > "CRITICAL SERVICE". I want to avoid Nagios checks any service in DOWN > host. > Please, how can I get it? > I want Nagios don't execute any service check until host is UP again.
Nagios doesn't send any service notification for down host. If that's not enough use an eventhandler to disable active services checks on the host. See the Nagios documentation about "event handlers" and "Adaptive Monitoring". If you do so, use Nagios 3.x and make sure you have regularly scheduled hosts checks or your service will never get back up (nagios generally use service results as a trigger to hosts checks, though nagios3 added scheduled host checks and result caching). - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJo03O6dZ+Kt5BchYRAvnvAJ4n+FME6lkWaxWDWpAFchHzgq0WpQCgqLy1 qW+glM2Lt+ZtccflllCTaZk= =PuNL -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Nagios-users mailing list Nagios-users@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
