[dev.icinga.com #2195] host_check, last_check == next_check; services scheduled too often #821
Comments
Updated by ricardo on 2011-12-13 23:03:04 +00:00 Another solution would be: |
Updated by mfriedrich on 2012-01-27 20:31:42 +00:00
|
Updated by skysurferjh on 2012-02-05 12:34:25 +00:00 Nach einem Update von Icinga 1.5.1 auf 1.6. inklusive der IDO-Utils und Icinga-Web haben wir den gleichen Fehler. In der Classic-GUI (in der Scheduling Queue) stehen die gleichen Uhrzeiten bei "Last Check" und "Next Check". Allerdings sind wir nicht davon betroffen, das auch bestimmte Host Checks in der "Scheduling Queue" hängen bleiben. Klickt man auf einen einzelnen Host- oder Service-Check, stehen dort die korrekten Zeiten. |
Updated by mfriedrich on 2012-05-05 14:43:11 +00:00 within
happens the logic to determine the freshness of the checkresults.
mainly for that reason the next_check attribute is set to start_time when invoking a non-scheduled on demand check, and not somewhere undeterministic in the future, between regular scheduling intervals. probably it would be better to mark a host check as non scheduled and check that flag, rather than passing strange time values around, marking wrong next_check values. orphaned checks are scheduled by event id EVENT_ORPHAN_CHECK
after scheduled host checks are put into the execution queue. when actually executing a host check, which could be on-demand as well....
you will then run into the next_check reset in order to bypass the orphaned check logic.
given that calculations, an on demand host check will trigger the following time start_time + latency + timeout + reaper_interval + 600s which will of course never reach the if condition match, as this is being reaped after running the check, and not having a future check somewhere. there are 2 options i can see:
the more simply solution is gui, the more clean is core. |
Updated by mfriedrich on 2012-05-13 17:30:28 +00:00
|
Updated by mfriedrich on 2012-09-18 12:11:17 +00:00
guess, a short time removal to be tested could be safe. though, consider it for 1.9 tree then. http://tracker.nagios.org/view.php?id=270 https://github.com/dnsmichi/nagios-svn/commit/3c5e689fc12df4e8f3f2b5a7b726e8ca49c13612 |
Updated by Anonymous on 2013-03-10 15:56:12 +00:00
Applied in changeset 5074e8d. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2195
Created by mfriedrich on 2011-12-13 22:27:11 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2013-03-10 15:56:12 +00:00)
Target Version: 1.9
Last Update: 2013-03-10 15:56:12 +00:00 (in Redmine)
http://tracker.nagios.org/view.php?id=270
Attachments
Changesets
2013-03-10 13:33:24 +00:00 by (unknown) 5074e8d
The text was updated successfully, but these errors were encountered: