Fix: Avoid Linux Agent timeouts when systemd-timedated doesn't run #790
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General information
See https://forum.checkmk.com/t/linux-agent-issues-with-systemd-timedated-service-creates-timeouts/52259 for context
Bug reports
When the Linux agents checks systemd-timesync, it calls
timedatectl show
:checkmk/agents/check_mk_agent.linux
Line 1631 in 86cbbd3
When the service
systemd-timedated.service
doesn't run, the command times out and blocks the agent out for ~25 seconds:25 seconds is nearly half of the default 60 seconds agent timeout, so the agent reaches this timeout sometimes when systemd-timedated is down.
Proposed changes
Add a
timeout
call to reduce the timeout fromtimedatectl show
from ~25 seconds to 5 seconds.