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 #9060] Alert config reload failures with the icinga check #2896
Comments
Updated by mfriedrich on 2015-04-29 16:08:02 +00:00 By flagging it as dirty only, or by adding a timestamp with the last failure allowing the caller to determine the delta himself? |
Updated by mfriedrich on 2015-10-30 23:43:02 +00:00
|
Updated by mfriedrich on 2015-10-30 23:43:25 +00:00
|
Updated by mfriedrich on 2015-11-02 09:17:04 +00:00 The parent process waits for the child on reload, if that action fails the local icinga check should return the warning state. This sends back a check result to the master. |
Updated by mfriedrich on 2016-02-24 20:06:00 +00:00
|
Updated by mfriedrich on 2016-02-24 23:32:20 +00:00
|
Updated by mfriedrich on 2016-04-07 10:38:32 +00:00
|
Updated by gbeutner on 2016-05-11 14:09:25 +00:00
|
Updated by gbeutner on 2016-05-11 14:09:33 +00:00
|
Updated by gbeutner on 2016-05-11 14:10:03 +00:00
Applied in changeset 1ad4d9c. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9060
Created by mfrosch on 2015-04-14 13:33:47 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-05-11 14:10:03 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-11 15:24:35 +00:00 (in Redmine)
If an satellite or config receiver fails reloading the new configuration this is only logged inside the logfile of the host.
We should add the information as an critical error when running the Icinga check, either locally or via command_endpoint.
So the system recognizes the failure and displays it to the user.
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: