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 #10156] Client and server check states do not match #3405
Comments
Updated by mfriedrich on 2015-09-20 11:24:34 +00:00
The master log greps for sql queries for a specific string (which is not necessarily the same service). I fail to see how the check plugin execution only would correlate to the service state history. There could be different service checks being run, and confusing the execution log. Make sure to 1) compare service objects and their timestamps 2) check the state change history backend on the master. |
Updated by henti on 2015-09-21 06:02:41 +00:00 dnsmichi wrote:
Good morning. I compared the objects, but could not find any timestamp data. Could you please direct me in the right direction. output from icinga2 object list below : Master
Client
The state history on the master corresponded with notifications we were seeing.
|
Updated by mjbrooks on 2015-10-05 09:30:12 +00:00
Hello @dnsmichi Same story with this one, @henti pinged me on IRC, he was wondering if you'd seen his feedback and was concerned. I can't seem to change the status back to open so I'm dropping it back in your lap and leaving it as feedback (sorry... again) |
Updated by mfriedrich on 2015-10-05 11:43:17 +00:00
Same story here - don't change assignees, we'll deal with feedback issues on a regular interval ourselves. |
Updated by henti on 2015-11-16 09:15:09 +00:00 dnsmichi wrote:
Any update on this bug ? Regards |
Updated by mfriedrich on 2016-02-24 23:15:10 +00:00
Which in term means that the replay log including the check results was not replayed properly. I haven't seen such issues with the recent 2.4.3 release, please test that. |
Updated by mfriedrich on 2016-03-18 17:14:40 +00:00
We consider this being fixed with 2.4.3+. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10156
Created by henti on 2015-09-16 10:31:35 +00:00
Assignee: (none)
Status: Closed (closed on 2016-03-18 17:14:39 +00:00)
Target Version: (none)
Last Update: 2016-03-18 17:14:39 +00:00 (in Redmine)
We had an outage on our monitoring system and since the recovery the state on two services on a remote client keeps changing state resulting in notifications.
I investigated and found that the server and client do not match in service states. The two checks is a proc check for dbsrv12 and a puppet agent check we wrote. the master is in GMT+2 and the client in GMT. below are extracts from the debug logs for the dbsrv12 proc check.
Master
Client
The output of the check command
Attachments
The text was updated successfully, but these errors were encountered: