New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #9997] "icinga" check should have state WARNING when the last reload failed #3321
Comments
Updated by seferovic on 2015-08-26 09:10:55 +00:00 Wouldn't you see that the zone is disconnected on the master? Or you could check the agent port on the remote machine? |
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-27 14:27:37 +00:00
|
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 lbetz on 2015-08-31 20:25:58 +00:00
Icinga got a reload from i.e. the master instance, the validation failed and a warning thru the cluster-zone check would be fine, immediately I think. |
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 mfriedrich on 2015-09-05 11:01:13 +00:00
|
Updated by gbeutner on 2015-11-14 18:45:24 +00:00
|
Updated by gbeutner on 2015-11-14 18:45:29 +00:00
|
Updated by mfriedrich on 2016-01-22 14:56:43 +00:00
|
Updated by mfriedrich on 2016-02-24 23:32:07 +00:00
|
Updated by mfriedrich on 2016-02-24 23:32:19 +00:00
|
Updated by gbeutner on 2016-05-11 14:08:36 +00:00
|
Updated by gbeutner on 2016-05-11 14:09:06 +00:00
|
Updated by gbeutner on 2016-05-11 14:10:04 +00:00
Applied in changeset 1ad4d9c. |
Updated by tobiasvdk on 2016-07-06 07:48:08 +00:00
|
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
Assignee: gbeutner
Status: Resolved (closed on 2016-05-11 14:10:04 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-11 14:10:04 +00:00 (in Redmine)
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?
Attachments
Changesets
2016-05-11 14:07:28 +00:00 by gbeutner 1ad4d9c
2016-05-12 09:11:03 +00:00 by gbeutner ff24863
Relations:
The text was updated successfully, but these errors were encountered: