-
Notifications
You must be signed in to change notification settings - Fork 579
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 #8333] Icinga2 master doesn't change check-status when "accept_commands = true" is not set at client node #2586
Comments
Updated by gbeutner on 2015-02-02 07:22:02 00:00
|
Updated by gbeutner on 2015-02-03 14:42:21 00:00
|
Updated by gbeutner on 2015-02-05 09:21:21 00:00
|
Updated by gbeutner on 2015-02-05 14:18:28 00:00
|
Updated by Anonymous on 2015-02-05 14:18:44 00:00
Applied in changeset 2d5112c. |
Updated by gbeutner on 2015-02-05 14:18:55 00:00 Please test whether this is fixed. |
Updated by gbeutner on 2015-02-05 14:38:00 00:00
|
Updated by mfriedrich on 2015-02-09 15:35:38 00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8333
Created by nuts on 2015-02-01 17:43:47 00:00
Assignee: gbeutner
Status: Resolved (closed on 2015-02-05 14:18:44 00:00)
Target Version: 2.3.0
Last Update: 2015-02-13 07:10:46 00:00 (in Redmine)
Icinga2 master and client node are configured for remote-check-execution like here [1].
Two szenarios:
(1) When "accept_commands = true" is missing in api.conf on the client, the master reschedule the remote check again and again. The state is pending. (thats not the bug but a question of concept)
(2) When a check successed with OK ("accept_commands = true" is set) and then "accept_commands = true" removed from the client node api.conf the master didn't change the check-status and check-output. The master can't get informations from the client node because the client node does not accept commands. But the master shows the old status with OK.
I think it would be better for the first szenario that the icinga2 master reports that commands are not allowed on the asked client node. For the secound szenario the check-state and output is wrong.
It is reproduceable with a working config on master and client and a configured remote check via remote-check-execution. When it works fine remove "accept_commands = true" from the client node api.conf.
[1] http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/monitoring-remote-systems#icinga2-remote-monitoring-client-command-execution
Changesets
2015-02-05 14:17:56 00:00 by (unknown) 2d5112c
2015-02-05 14:38:13 00:00 by (unknown) ddce723
Relations:
The text was updated successfully, but these errors were encountered: