Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #5671] Passive check result processing for host checks is not working #1429
This issue has been migrated from Redmine: https://dev.icinga.com/issues/5671
Created by mhoyer on 2014-02-18 10:51:24 +00:00
I recently updated our testing environment from Icinga 1.10.1 to 1.10.3 and our integration tests came up with an error. Flagging a host as "Down" using passive check results is not working any more.
Issued in icinga classic gui the "submit passive check result for this host" button sets status_code to 1. This leads to a host-down state in icinga 1.10.1 but not in 1.10.3. Looking at the logs it seems as if the passive check result is lost on interpretation.
This behavior matches documentation at http://docs.icinga.org/latest/de/pluginapi.html in "11.1.3. Return-Code". But without changing anything at the parameter "use_aggressive_host_checking=0", the behavior changed on update.
2014-02-18 12:03:36 +00:00 by (unknown) edc4645
2014-03-03 19:33:46 +00:00 by (unknown) 91e5d6e
2014-03-03 21:34:07 +00:00 by (unknown) 2e60399
2014-03-27 22:53:44 +00:00 by (unknown) 4ae54be
Updated by mfriedrich on 2014-02-18 11:12:06 +00:00
I fail to see how that is not working. #5575 fixes a long lasting bug improperly handling passive check results for host checks allowing users to set "1" without re-interpretation for host check results by the core itself.
Updated by mhoyer on 2014-02-18 11:25:37 +00:00
Updated by mfriedrich on 2014-02-18 12:07:47 +00:00
Ok. So the external commands are treated as passive checkresults, and they already provide the translated state. The plugin api reference is invalid, that's just true if the plugin is executed by the core itself.