Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #9033] freshness checks ignore service dependencies #1549

Closed
icinga-migration opened this issue Apr 9, 2015 · 2 comments
Closed

Comments

@icinga-migration
Copy link

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

Created by trish on 2015-04-09 10:09:33 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-05-18 12:18:16 +00:00 (in Redmine)

Icinga Version: 1.11.6-1~bpo70+1
OS Version: Debian Wheezy

Seems to be an old bug inherited from Nagios (http://osdir.com/ml/network.nagios.devel/2004-05/msg00003.html): When a service dependency tells a service to stop checking in dependence of another check satellites happily obey this command. The master, however, finds out that no check results are being delivered by the satellites, and finally sets in with freshness checks, completely ignoring the service dependencies.

This is really bad in cases when the dependency is defined in order to prevent hanging check procs to pile up on the monitored host. Disabling freshness, on the other hand, is no issue as the master should take over checks in case a satellite is failing to check or to report.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-04-26 07:31:01 +00:00

I partly understand the issue, but I don't think there's an easy solution for that. Either disable freshness checks on the master, or fix the freshness code taking dependencies into account. For the latter I am not sure how much impact this one has (patch, tests, changes?).

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:18:16 +00:00

  • Target Version set to Backlog

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@dnsmichi dnsmichi removed this from the Backlog milestone Dec 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants