From: Ton Voon <ton.voon@op...> - 2013-09-24 09:00:58
Looking at the latest Nagios code, our automated tests have picked up that if a host or a service's check_interval is set to 0, it is changed to 1.0. This appears to be from commit f99a9a7b which says:
Author: Andreas Ericsson <ae@...>
Date: Wed Aug 14 01:35:19 2013 +0200
core: Disallow zero retry- or check-intervals
If we *do* have zero retry or check-intervals and happen to disable
checks of the type that we have zero intervals for, we'll keep on
scheduling and rescheduling the same checks over and over to run at
the exact same timestamp, which will only cause us to peg the cpu
at 100% and log insane amounts of data to the debug log. Not so hot,
so let's avoid it whenever possible.
Signed-off-by: Andreas Ericsson <ae@...>
For hosts, check_interval=0 with active_checks_enabled=1 means "do not regularly check this host but check on demand", this change suggests this is no longer possible.
Is this deliberate? If so, is this behaviour supported in a different way or is it recommended to not use have check_interval=0 anymore.
Get latest updates about Open Source Projects, Conferences and News.