<br><font size=2 face="sans-serif">You hit it on the nose.. I am using
host templates, so I'll just leave it like that. I forgot that it
checks in that fashion.</font>
<br>
<br><font size=2 face="sans-serif">_____________________________<br>
SUNY - ITEC<br>
Information Technology Exchange Center<br>
Systems Programmer/Analyst<br>
E-mail: Joe.Hoot@itec.suny.edu<br>
Office: (716)878-4644<br>
Cell: (716)908-6292<br>
Fax: (716)878-3485<br>
_____________________________</font>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Chester R. Hosey"
<Chester.Hosey@gianteagle.com></b> </font>
<p><font size=1 face="sans-serif">08/08/2005 10:59 AM</font>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">Joe.Hoot@itec.suny.edu</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top><font size=1 face="sans-serif">nagios-users@lists.sourceforge.net</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: [Nagios-users] servicedependencies
and all services being dependent on
PING</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>On Mon, 2005-08-08 at 10:34 -0400, Joe.Hoot@itec.suny.edu
wrote:<br>
> <br>
> I'm trying to do the following: <br>
> <br>
> define servicedependency{ <br>
> host_name
admoraprod <br>
> service_description
PING <br>
> dependent_host_name
admoraprod <br>
> dependent_service_description *
<br>
> execution_failure_criteria
n <br>
> notification_failure_criteria w,u,c
<br>
> } <br>
> <br>
> This complains about a loop being created by this, wheras PING is
now<br>
> dependent on PING. <br>
> <br>
> Well, basically what I want is to say that if the host goes down(can't<br>
> be pinged) then don't report on any other services. Does anyone
know<br>
> a good way to do this? Previously I was creating a servicedependency<br>
> definition for every server for every host. This was becoming
a lot<br>
> of work to do. <br>
> <br>
> Any suggestions are welcome. <br>
> <br>
> Thanks, <br>
> Joe <br>
<br>
<br>
Curse Evolution's reply behavior. Now with cc-list goodness.<br>
<br>
Have you specified a check_command in the host definition? If one is<br>
specified, when a service check fails, Nagios will run the host<br>
check_command and suppress reporting failures of other service checks on<br>
the host.<br>
<br>
define host{<br>
name
generic-host<br>
notifications_enabled
1<br>
event_handler_enabled
1<br>
flap_detection_enabled
1<br>
failure_prediction_enabled 1<br>
process_perf_data
1<br>
retain_status_information
1<br>
retain_nonstatus_information 0<br>
register
0<br>
check_command
check-host-alive<br>
}<br>
<br>
<br>
define command {<br>
command_name check-host-alive<br>
command_line $USER1$/check_ping
-H $HOSTADDRESS$ -w<br>
3000.0,80% -c 5000.0,100% -p 1<br>
}<br>
<br>
<br>
All of my hosts inherit ("use") generic-host. If you're not into<br>
templates, specify "check_command check-host-alive" in each host<br>
definition.<br>
<br>
Or am I missing your intent?<br>
<br>
<br>
<br>
</tt></font>
<br><font size=2 color=white face="sans-serif">ForwardSourceID:NT000183E2
</font>