Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I'm seeing the following in the boot log:
systemd[1]: Userspace Out-Of-Memory (OOM) Killer was skipped because of a failed condition check (ConditionPathExists=/proc/pressure/memory).
<repeats 18 times>
systemd[1]: Userspace Out-Of-Memory (OOM) Killer was skipped because of a failed condition check (ConditionPathExists=/proc/pressure/memory).
systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation.
systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'.
Other services emitting the "... was skipped because ..." messages don't seem to hit this issue, so I'm assuming this is something oomd specific.
This started failing recently, there was no error (and no "was skipped" messages) in systemd-249-9.el9 and I observed it failing with systemd-250-3.el9.
Version-Release number of selected component (if applicable):
systemd-250-3.el9
v250 added socket activation for systemd-oomd and the socket is getting activated during boot, even though it's not enabled.
(It's a separate question why have you installed systemd-oomd but haven't enabled PSI, which is off by default in RHEL...)
(In reply to David Tardon from comment #1)
> v250 added socket activation for systemd-oomd and the socket is getting
> activated during boot, even though it's not enabled.
It turns out this is not really true. It's systemd-oomd.service that pulls systemd-oomd.socket in (because it requires it); systemd-oomd.service itself is pulled by user@.service because systemd-oomd package installs an override config. file that sets ManagedOOMMemoryPressure=kill.
Anyway, the reported problem is something that can be easily fixed by enabling PSI (or not installing systemd-oomd if one doesn't want to use it), therefore I don't think there's anything here we need to do.