Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #11825] Problems with check scheduling for HARD state changes (standalone/command_endpoint) #4232
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11825
Created by mfriedrich on 2016-05-21 16:51:25 +00:00
x. SOFT state -> retry_interval
2016-05-21 16:58:19 +00:00 by mfriedrich d49b63d
2016-05-24 09:05:29 +00:00 by gbeutner aeb7a4a
2016-05-24 10:42:02 +00:00 by gbeutner 7b371f2
Updated by mfriedrich on 2016-05-21 16:58:09 +00:00
We need to check whether a hardChange occurred when updating the next check. Using UpdateNextCheck() does not help here as it will include the scheduling offset.
Testing a possible fix with a shorter interval range (check_interval = 60s, retry_interval = 30s).
Updated by mfriedrich on 2016-05-24 11:21:00 +00:00