(no subject)

[Marc Powell]

The host is still up because, as you said, you didn't define a host check command for it. Since nagios has no active test defined to see if a host is up, the state will never change. The hosts are 'assumed to be up' initially because if the very first check of any service on that host is OK then the host is assumed to be OK. It's only when a service on that host changes state (i.e. goes CRITICAL), only then is the host actively checked with the command specified (or not in your case).

In short, you _must_ define a host check command if you expect your host states to be accurately reflected.

--
Marc 

________________________________________
From: Alexis Chauvin [mailto:Alexis.chauvin at courtsplc.com] 
Sent: Thursday, September 25, 2003 10:32 AM
To: nagios-users at lists.sourceforge.net

Hi, I have check in the documentation and in the FAQ,
But I can't find what's the relation between host and service.
 
Explaination : 
 
I didn't define any check command in the host.cfg file.
So "Pending" is written in the web interface.
After a while, when services are checked as OK,  every "Host assumed to be up".
But, when I turn down the service, and when I have only one service running on the machine,
The service become critical (simple ping for example), but the host is still up !!
 
Any idea ? 
 
Thanks very much
 
 
 
Alexis Chauvin
International IT
tel +44(0)2084109476
 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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