[dev.icinga.com #540] potential bug in distributed environments: passive checks are checked actively #264

icinga-migration opened this Issue Jun 25, 2010 · 6 comments


None yet
1 participant

icinga-migration commented Jun 25, 2010

This issue has been migrated from Redmine: https://dev.icinga.com/issues/540

Created by mstreb on 2010-06-25 13:48:43 +00:00

Assignee: (none)
Status: Closed (closed on 2010-08-04 15:10:49 +00:00)
Target Version: (none)
Last Update: 2010-08-04 15:10:49 +00:00 (in Redmine)

under some, actual not known circumstances the following is happening:

in an distributed environment the central instance which is just accepting passive checks is executing active servicechecks even if active_checks_enabled is set to 0.
In this case also the retention file is not showing any setting which is enabling the active checks.

has anybody an idea how this could happen, neither freshness checking nor an dependency is configured for this service.


icinga-migration commented Jun 28, 2010

Updated by mfriedrich on 2010-06-28 08:48:14 +00:00

is it possible that the template used for this service has active_checks_enabled? this is the only condition matching regarding config parsing.


icinga-migration commented Jul 2, 2010

Updated by mstreb on 2010-07-02 10:34:35 +00:00

nop, i checked this more than once.
also in objects.cache its set to 0

but maybe it has something to do with the check_freshness stuff i will recheck this.

-> this is why i opened a potential bug report. :)



icinga-migration commented Jul 4, 2010

Updated by Meier on 2010-07-04 15:58:07 +00:00

To log freshness debug info set debug_level to 16 (DEBUGL_CHECKS) and debug verbosity to 1 or 2.


icinga-migration commented Jul 9, 2010

Updated by mfriedrich on 2010-07-09 14:46:24 +00:00

  • Category changed from Other to Distributed

icinga-migration commented Aug 4, 2010

Updated by mfriedrich on 2010-08-04 14:42:36 +00:00

  • Priority changed from Normal to Low

any updates on that?


icinga-migration commented Aug 4, 2010

Updated by mstreb on 2010-08-04 15:10:49 +00:00

  • Status changed from New to Closed

yep as always: the problem is behind the display
-> global freshness checking was enabled.

Issue an be closed, i totally forgot about that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment