Am 14.12.21 um 23:08 schrieb Garry T. Williams:
On Tuesday, December 14, 2021 3:19:10 AM EST Ralf Corsépius wrote:
On all of my machines, I am seeing long sequences similar the logs:
Dec 14 09:12:01 lewis systemd[1]: systemd-oomd.service: Scheduled restart job, restart counter is at 384.
Dec 14 09:12:01 lewis systemd[1]: systemd-oomd.service: Failed with result 'timeout'.
Dec 14 09:11:20 lewis systemd[1]: systemd-oomd.service: start operation timed out. Terminating.
Dec 14 09:09:50 lewis systemd[1]: systemd-oomd.service: Scheduled restart job, restart counter is at 383.
Any ideas what this means and what to do about/against it?
That service has Restart=on-failure defined, so that explains the
message "Scheduled restart job, restart counter is at 383".
FWIW: The "restart counter" went up ca. once per minute blowing up
journals beyond reasons.
The only clue to why it's failing is 'timeout'. Connecting to the bus
is the only thing I can think of. No idea why.
My wild guess is, something "oom'ed" and this systemd-oom thing failed
to forward it to something, periodically retrying ad infinitum.
Big questions: Which bus and what oomed?
I regret having to say so, but in its present shape systemd-oomd is a
not helpful at all, IMO.
Finally, with today's kernel update (and subsequent reboot) the issue
seems to have vanished (at least until now) ?!?
Ralf
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
