Host check doesn't wait in-between checks.

[Marc Powell]

> -----Original Message-----
> From: Samba [mailto:Samba at guidemail.com]
> Sent: Monday, June 05, 2006 9:55 AM
> To: nagios-users at lists.sourceforge.net
> Cc: Marc Powell
> Subject: RE: [Nagios-users] Host check doesn't wait in-between checks.
> 
> Maybe I'm dense, but isn't Nagios doing the checks in parallel if it's
> running 3 host checks on the same host at exactly the same time?

I've just re-examined the code in checks.c as a sanity check (yummy open
source). It's sequential, not parallel. The section starts at 2024 in
checks.c. The loops (2 depending on initial state) begin with  --

                /* retry the host check as many times as necessary or
allowed... */
 
for(hst->current_attempt=1;hst->current_attempt<=max_check_attempts;hst-
>current_attempt++){

                        /* check the host */
                        result=run_host_check(hst,check_options);

> What is the point of setting a Host max_check_attempts if Nagios isn't
> going to wait in between checking?

Maybe you don't feel one check is enough to determine host state. Maybe
your host check is such that it does something active the first time and
verifies it the second time. Maybe you just like being really really
sure a host is down. Think flexibility for those cases you don't know
about or implement.
 
> Not trying to be a pain, I just want to understand.  I was thinking
that
> if I set the max_check_attempts to 3 it should try the check 3 times
> (one at a time) before telling me the host is down.

That is what it's doing.

--
Marc


_______________________________________________
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