<div>On 8/17/06, Marc Powell <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > -----Original Message----- > From: <a href="mailto:nagios-users-bounces@lists.sourceforge.net">nagios-users-bounces@lists.sourceforge.net</a> [mailto:<a href="mailto:nagios-users-">nagios-users-</a> > <a href="mailto:bounces@lists.sourceforge.net">bounces@lists.sourceforge.net</a>] On Behalf Of Danil Kutepkin > Sent: Thursday, August 17, 2006 3:50 AM > To: <a href="mailto:nagios-users@lists.sourceforge.net"> nagios-users@lists.sourceforge.net</a> > Subject: [Nagios-users] host check anly after critical service check > > Hello nagios-users, > > How to make a host active check (ping) only after a failed service > check (ping)? </blockquote></div> I don't follow either. Some hosts you may only want to set up a service "PING", but you want the host to also be checked so that you get a single HOST failure, vs a service failure if the host is down. So setup the host with a check_command check-host-alive line, and then add a service for the same host define service{ use generic-service host_name hostname service_description Ping check_command check-host-alive If the service check fails, it will force the hose to do a host check, and since well it's probably down, you should only receive a host critical/unreachable alert. Sorry if your not really talking this basic, then your going to have to provide a bit more information. You could also force the host to actually be checked like a service by enabling active checks every x minutes (create a new host template)