Nagios lying about host status?

Marc Powell marc at ena.com
Tue Jan 2 22:29:18 CET 2007



> -----Original Message-----
> From: nagios-devel-bounces at lists.sourceforge.net [mailto:nagios-devel-
> bounces at lists.sourceforge.net] On Behalf Of Ahmon Dancy
> Sent: Tuesday, January 02, 2007 3:18 PM
> To: Christoph Maser
> Cc: nagios-devel at lists.sourceforge.net
> Subject: Re: [Nagios-devel] Nagios lying about host status?
> 
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Please read
> >>
http://nagios.sourceforge.net/docs/2_0/checkscheduling.html#host_checks
> 
> Read it.
> 
> It claims: "One instance where Nagios checks the status of a host is
> when a service check results in a non-OK status".
> 
> That statement could use some clarification.  Does it check the host
> status each time a service check results in a non-Ok status, or only
> when the service status changes?  (The former would be more
> reasonable, IMHO, but the latter is what appears to be the case).

Only when a service changes state. With the current serialized host
checks there could be significant performance penalties to check host
status at every non-OK service check, especially if you have many hosts
down. If any service on the host changes state then the host is checked.
If any service on the host is up then the host is assumed to be up (for
initial checks). If you only monitor one service on the host then the
host will only be checked when that service changes state. In your case,
it would appear that you only monitor one service on that host so the
behavior you saw is considered normal.

--
Marc 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV




More information about the Developers mailing list