Host checks not working on certain hosts

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Wouter Mignon
> Sent: Thursday, March 09, 2006 8:10 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Host checks not working on certain hosts
> 
> Hello,
> 
> I have a few switches that don't have any services attached, some of
> them do their host-check and i receive mail/sms when they have are
> unreachable but a few stay in PENDING state and don't seem to do any
> checks. What could be wrong?
> 

Nagios is first-and-foremost a service monitor. With few exceptions*,
host checks are never executed unless a service on that host returns a
non-OK state. You need to have at least one service defined per host if
you want it to be checked regularly. That service could be just another
ping check. As to why some show OK and others show PENDING, I would
speculate that they are listed as the parent for a device that has
failed in the past. Nagios will check the host status of parents to
determine if a child is down or unreachable due to higher level outages.

* Starting with Nagios 2.0 you _can_ have regularly scheduled host
checks but they affect performance and are discouraged. The parent
checks are another case where a host check may be executed without a
failure of a service on the device.

--
Marc 


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
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