-
Notifications
You must be signed in to change notification settings - Fork 581
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
1 day is only 23h #10255
Comments
First, this looks kinda strange. So strange that I verified at an own setup that a daily Service check there was actually scheduled 24 hours after the last run. Could you please provide some more insights by running the following commands as your usual Icinga 2 user. Please alter the object name in the second command accordingly.
As you have timestamps in your database, would it be possible for you to go further back and verify if this has happened since "always" or if this is a more recent development? Furthermore, being scheduled exactly at 06:00 seems a bit odd. Is there something rescheduling checks? |
This seems to be the normal check scheduler behavior as also documented here. icinga2/lib/icinga/checkable-check.cpp Lines 52 to 79 in 4b884ea
However, without having to investigated this further, there seems to be a difference between this code block and the linked documentation. Could you temporary enable debug logs and wait for the matching "Update checkable" log message with its surrounding messages? |
here you go:
|
Describe the bug
I recently noticed something strange using the following config:
My selenium icingaweb2 module writes to a database so I know the time the check is actually executed and the time between two checks is not 24h but only 23h
To Reproduce
Screenshots
Selenium check:
Monitoring module:
IcingaDb module:
Your Environment
Include as many relevant details about the environment you experienced the problem in
icinga2 --version
): 2.14.3icinga2 feature list
):icinga2 daemon -C
):zones.conf
file (oricinga2 object list --type Endpoint
andicinga2 object list --type Zone
) from all affected nodes.Best Regards
Nicolas
The text was updated successfully, but these errors were encountered: