You are not logged in.
Hey friends! Thanks for reading, appreciate any help here.
I notice when I boot that systemd-oomd.socket is failing to load. This hasn't always been the case, however I don't know when this might have started to happen as I don't check for failed systemd startup units every time I boot (maybe I should).
$ sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-oomd.socket loaded failed failed Userspace Out-Of-Memory (OOM) Killer Socket
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
However a simple restart of of systemd-oomd fixes this. What steps do folks recommend here to troubleshoot?
For the record I haven't done any specific configuration of the service or anything, just enabled and forgotten it long ago.
Thanks.
Offline