Thomas Guyot-Sionnest a écrit:
On 23/02/09 10:43 AM, Sergio Ariel wrote:
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
Nagios doesn't send any service notification for down host.
But the Nagios WEB console still displays FAILED or UNKNOWN status for
individual service cheks. You have to filter out all the results by
hand, to see what are the 'source' problems (ie, a router down) and what
are just 'cascaded' problems (lots of failed service checks due to
unreachability of hosts located over the router). These 'cascaded'
results are generating unuseful 'noise' which complicates the overall
reading of the console. IMHO, in such a situation, what the Nagios
console displays is inaccurate.
If that's not enough use an eventhandler to disable active services checks
It's still not enough :-) Service checks scheduled before the event
handler triggers will still display inaccurate 'FAILED' status.
Any idea to go further is welcome. Kind regards,
--
*Toussaint OTTAVI*
*MEDI INFORMATIQUE*
**
------------------------------------------------------------------------------
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
