This is normal, due to the fact that NetSaint/Nagios only checks a =
host's status if/when there is a service problem.
Documentation on this can be located at =
http://www.nagios.org/docs/1_0/networkreachability.html.
I don't believe that it specifically mentions the 'Host Assumed to be =
Up' message, but otherwise explains this feature quite well.
Garry W. Cook, CCNA
Network Infrastructure Manager
MACTEC, Inc. - http://www.mactec.com/
303.308.6228 - 303.881.5157
> -----Original Message-----
> From: John Radopp [mailto:j.radopp@job4me.de]
> Sent: Monday, April 29, 2002 9:41 AM
> To: nagios-devel@lists.sourceforge.net
> Subject: [Nagios-devel] Bug: Funny host checking behavior
>=20
>=20
>=20
> I am observing a non-documented behavior regarding the host checks.
> Some of the machines are declared as "Host assumed to be up". The
> check command is apparently never executed for these machines.
>=20
> For some of the other hosts the checks returns the correct values.
>=20
> After thinking and tweaking a little I found out that if I create an
> arbitrary warning (e.g. set nrpe disk space warning level to 10%) on
> one of the "assumed to be up" hosts then the command is executed
> properly.
>=20
> The hosts being correctly pinged are the ones having alerts.
>=20
> Regards,
>=20
> John
>=20
>=20
>=20
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/lis ... gios-devel
>=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: Garry.Cook@mactec.com