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 #11248] Active checks are executed even though passive results are submitted #3985
Comments
Updated by julianbrost on 2016-02-27 18:38:14 +00:00 Michael Friedrich pointed out, that passive checks are enabled by default and thus that if (as proposed in my patch) would be triggered almost all the time. I guess one would want to add
to the condition but I didn't test that so far. |
Updated by mfriedrich on 2016-02-27 19:04:55 +00:00
|
Updated by mfriedrich on 2016-02-29 09:00:10 +00:00
|
Updated by mfriedrich on 2016-03-04 15:27:37 +00:00
|
Updated by mfriedrich on 2016-03-04 15:30:36 +00:00
|
Updated by mfriedrich on 2016-03-04 15:33:12 +00:00
|
Updated by mfriedrich on 2016-03-04 15:33:36 +00:00
|
Updated by mfriedrich on 2016-03-05 17:39:59 +00:00 I've reverted 2 commits which might be causing trouble here. Can you please re-test the current git master? |
Updated by mfriedrich on 2016-03-09 10:42:18 +00:00
In terms of cr~~GetActive()~~ good idea, we discussed that today independent of this issue. A proper fix for the retry_interval should take that into account with #11336. In the meantime I'll assign this issue for 2.4.4 - it'll be great if you could do further tests, allowing this ticket being resolved for the targeted release. |
Updated by mfriedrich on 2016-03-09 10:44:08 +00:00
|
Updated by julianbrost on 2016-03-10 13:26:17 +00:00 Seems to be fixed. I can't reproduce the problem with version 68449c2. |
Updated by mfriedrich on 2016-03-11 08:35:00 +00:00
Thanks. |
Updated by mfriedrich on 2016-03-11 14:55:23 +00:00
|
Updated by mfriedrich on 2016-03-24 09:37:51 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11248
Created by julianbrost on 2016-02-27 18:24:55 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-03-11 08:35:00 +00:00)
Target Version: 2.4.4
Last Update: 2016-03-24 09:37:51 +00:00 (in Redmine)
If a service is defined using the following template and passive check results are submitted every 5 minutes, Icinga will still run the active check every 17 minutes and set the status to unknown causing the service to flap all the time.
The next check time gets impropery updated:
At (1) passive check results were submitted but the next check time wasn't updated, at (2) Icinga executed the scheduled check even though passive results were submitted a few seconds earlier, in this case the next check time got updated.
This bug seems to be introduced by 9ca7245. I've attached a patch that fixes this issue.
Attachments
Changesets
2016-03-05 17:15:03 +00:00 by mfriedrich b8e3d61
2016-03-05 17:16:49 +00:00 by mfriedrich ef532f2
2016-03-11 14:55:03 +00:00 by mfriedrich 8344f74
2016-03-11 14:55:14 +00:00 by mfriedrich f99feab
The text was updated successfully, but these errors were encountered: