for that service. Ergo, if you set your service checks max to 15, after
15 minutes (assuming your delay is 60 seconds) your service will hit a
HARD CRITICAL, and host checks will fire.
That's not correct, host checks are performed as soon as a service check
returns some non-OK
Hi,
I have many hosts that are constantly giving me DOWN/UP state as they
are unreachable for certain periods. In an attempt to give the system more
time to become available, I increased the max_check_attempts from 2 to 5. At
2 the interval between retry attempts was 10 seconds. Now at 5,
I'd suggest NOT taking this action at the host level; reason being that all
service checks are halted for the duration of this non-parallelized
action... You want to avoid doing a host check until absolutely necessary.
Suggest increasing the max_check_attempts on the SERVICE to a larger number,
Thanks Eli,
According to the docs, Nagios checks the status of a host is when a service
check results in a non-OK status.. Is that when it reaches a HARD state
after all iterations of max_check_attempts are done or as soon as it goes to
non-OK (SOFT) state? If the latter, which seems to be
* Kyle Tucker [EMAIL PROTECTED] [2006-05-22 14:45]:
I have many hosts that are constantly giving me DOWN/UP state as they
are unreachable for certain periods. In an attempt to give the system more
time to become available, I increased the max_check_attempts from 2 to 5. At
2 the interval
Am Montag 22 Mai 2006 22:44 schrieb Holger Weiss:
* Eli Stair [EMAIL PROTECTED] [2006-05-22 12:49]:
for that service. Ergo, if you set your service checks max to 15, after
15 minutes (assuming your delay is 60 seconds) your service will hit a
HARD CRITICAL, and host checks will fire.
