Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #9997] "icinga" check should have state WARNING when the last reload failed #3321
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9997
Created by lbetz on 2015-08-26 08:29:47 +00:00
If you have many agent/satellites in your setup and there is a configuration problem on some agents/satellites the reload failed. How I notice this? Maybe it's possible to add anything to the icinga plugin that inform the user with a warning?
2016-05-11 14:07:28 +00:00 by gbeutner 1ad4d9c
2016-05-12 09:11:03 +00:00 by gbeutner ff24863
Updated by lbetz on 2015-08-26 12:08:58 +00:00
The zone is still connected and icings is running. But the reload failed because you've a corrupt configuration, i.e. duplicate definitions. At this time the only chance to detect this, is to look into the log file. But it's important to know, if your new configuration isn't active on satellites or agents.
Updated by mfriedrich on 2015-08-31 15:13:27 +00:00
The question is rather - what would trigger a warning? last failed config validation within amount of time X (threshold)?
Updated by mfriedrich on 2015-09-05 11:01:03 +00:00
There's a problem with our cluster protocol only sending asynchronous notifications (e.g. sending a config update and waiting for an answer is not possible at this point). Not sure how satellites would be able to notify their (reload) state back to parent instances.
I totally understand the idea, but currently I don't have a good design in mind. Will discuss this with Gunnar when he's back.
Updated by gbeutner on 2015-11-14 18:45:24 +00:00