We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
232-25
Debian sid
No logs with kernel tag
Logs with kernel tag (via journalctl -k or dmesg):
journalctl -k
dmesg
Jun 08 14:41:11 server02 systemd[1]: apt-daily-upgrade.timer: Adding 55min 37.456860s random time. Jun 08 14:41:11 server02 systemd[1]: rkhunter.timer: Adding 35min 26.404897s random time. Jun 08 14:41:11 server02 systemd[1]: chkrootkit.timer: Adding 1h 34min 53.783802s random time. Jun 08 14:41:11 server02 systemd[1]: apt-daily-upgrade.timer: Adding 44min 28.509264s random time. Jun 08 14:41:11 server02 systemd[1]: rkhunter.timer: Adding 2h 33min 33.290440s random time. Jun 08 14:41:11 server02 systemd[1]: chkrootkit.timer: Adding 2h 51min 33.051365s random time.
Boot the system and trigger the random timer additions (e.g. via systemctl daemon-reload)
systemctl daemon-reload
Original bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864422
System properties
systemctl daemon-reexec fixes the problem
systemctl daemon-reexec
Standard configuration, besides Storage=persistent
Storage=persistent
The text was updated successfully, but these errors were encountered:
have you turned on "debug" logging mode in the kernel? What does "systemctl show" say about your log level when this happens?
Sorry, something went wrong.
With the upgrade to 233-9, the issue disappeared.
233-9
No branches or pull requests
Submission type
systemd version the issue has been seen with
232-25
Used distribution
Debian sid
Expected behaviour you didn't see
No logs with kernel tag
Unexpected behaviour you saw
Logs with kernel tag (via
journalctl -k
ordmesg
):Steps to reproduce the problem
Boot the system and trigger the random timer additions (e.g. via
systemctl daemon-reload
)Additional notes
Original bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864422
System properties
systemctl daemon-reexec
fixes the problemStandard configuration, besides
Storage=persistent
The text was updated successfully, but these errors were encountered: