-
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 #9016] Downtimes which have been triggered are not properly recorded in the database #2881
Comments
Updated by elippmann on 2015-04-09 09:01:09 00:00
|
Updated by mfriedrich on 2015-04-12 12:06:47 00:00
|
Updated by mfriedrich on 2015-04-12 12:37:58 00:00
Ok. That's actually a race-condition I've introduced with fixing the missing triggered downtime on schedule if the host/service is already in a NOT-OK state in #8389. lib/icinga/checkable-downtime.cpp
My fix from #9014 is partially fixing this problem by not setting the trigger_time on a newly added downtime, but depending on the TriggerDowntime() function to do that - we'll fix this here. Wrong
Fixed
|
Updated by mfriedrich on 2015-04-12 12:38:18 00:00
|
Updated by mfriedrich on 2015-04-12 12:41:55 00:00
|
Updated by Anonymous on 2015-04-12 12:43:26 00:00
Applied in changeset 37f2459. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9016
Created by elippmann on 2015-04-08 15:30:32 00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-04-12 12:43:26 00:00)
Target Version: 2.3.4
Last Update: 2015-04-12 12:43:26 00:00 (in Redmine)
If a downtime is triggered, Icinga 2 seems to update the
trigger_time
column only.debug.log wrote:
MySQL wrote:
Attachments
Changesets
2015-04-12 12:38:35 00:00 by (unknown) 37f2459
2015-04-12 12:41:30 00:00 by (unknown) e659784
Relations:
The text was updated successfully, but these errors were encountered: