<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Thomas Guyot-Sionnest a écrit: <blockquote cite="mid:49A34E13.80802@aei.ca" type="cite"> <pre wrap="">On 23/02/09 10:43 AM, Sergio Ariel wrote:</pre> <blockquote type="cite"> <pre wrap="">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</pre> </blockquote> <pre wrap=""> Nagios doesn't send any service notification for down host. </pre> </blockquote> 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. <blockquote cite="mid:49A34E13.80802@aei.ca" type="cite"> <pre wrap="">If that's not enough use an eventhandler to disable active services checks</pre> </blockquote> 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, <div class="moz-signature">-- <title>Signature</title> <meta http-equiv="Content-Type" content="text/html; "> <style type="text/css">  </style> Toussaint OTTAVI MEDI INFORMATIQUE </div> </body> </html>