Repository navigation
fix(linux): Timers Fire Again After A Reboot - #111
Merged
Merged
Conversation
The three systemd user timers set Persistent=true, which only serves OnCalendar=. With a stamp left from before a reboot, systemd treats the OnBootSec= trigger as already spent, so the timer never fires and OnUnitActiveSec= never gets a first run to count from. On photon this left the job board and both usage boards frozen for 17 hours after the box was stopped and started. Drops Persistent= from the templates; the installer test refuses it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Executive Summary
After a Linux box is stopped and started, its usage boards and job board stop updating until someone starts the services by hand. On photon they stayed frozen for 17 hours, so new photon jobs never showed in the statusline. This drops the setting that causes it.
Developer Summary
Persistent=true, which only applies toOnCalendar=. With a stamp left from before a reboot, systemd treatsOnBootSec=as already spent: the timer goesactive (elapsed)with no next trigger, andOnUnitActiveSec=never gets a first run to count from.OnBootSec=5and a stamp dated before the boot.Persistent=trueran 0 times;Persistent=falseran once.test/test_install_account_router.shnow fails if a Linux timer template setsPersistent=true. It failed before the fix and passes after.install-account-router.sh.