[Raspberry Pi/lunar] systemd-oomd fails with "ConditionControlGroupController=memory was not met"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Lunar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
PROBLEM SUMMARY:
----------------
Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionContr
If you manually started it after boot it starts but after a few minutes it fails with the same error.
These are the journalctl entries regarding this problem:
abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket.
abr 20 23:12:48 fpgrpi systemd[1]: systemd-
--- Line repeat 20 times ---
abr 20 23:12:49 fpgrpi systemd[1]: systemd-
abr 20 23:12:49 fpgrpi systemd[1]: systemd-
abr 20 23:12:49 fpgrpi systemd[1]: systemd-
This is the systemctl status for systemd-
# systemctl status systemd-
○ systemd-
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
TriggeredBy: × systemd-oomd.socket
Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago
└─ ConditionContro
Docs: man:systemd-
# systemctl status systemd-oomd.socket
× systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket
Loaded: loaded (/lib/systemd/
Active: failed (Result: trigger-limit-hit) since Thu 2023-04-20 23:21:07 CEST; 9h ago
Duration: 2min 2.252s
Triggers: ● systemd-
Docs: man:systemd-
Listen: /run/systemd/
ADITIONAL INFO:
---------------
Machine is an arm64 "Raspberry Pi 4 Model B Rev 1.4 8GB"
# uname -a
Linux fpgrpi 6.2.0-1004-raspi #5-Ubuntu SMP PREEMPT Mon Apr 3 11:15:14 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
# lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.04
Release: 23.04
# apt-cache policy systemd-oomd
systemd-oomd:
Instalados: 252.5-2ubuntu3
Candidato: 252.5-2ubuntu3
Tabla de versión:
*** 252.5-2ubuntu3 500
500 http://
100 /var/lib/
CVE References
tags: | added: linux-raspi raspberry-pi |
summary: |
- systemd-oomd fails with "ConditionControlGroupController=memory was not - met" + [Raspberry Pi/lunar] systemd-oomd fails with + "ConditionControlGroupController=memory was not met" |
tags: | added: kern-6572 |
Changed in systemd (Ubuntu): | |
status: | New → Invalid |
Changed in linux-raspi (Ubuntu Lunar): | |
status: | New → Fix Committed |
I see that memory cgroup is not enabled:
# cat /proc/cgroups | grep y
#subsys_name hierarchy num_cgroups enabled
memory 0 121 0
So a workaround is to enable it adding "cgroup_ enable= memory" to "/boot/ firmware/ cmdline. txt" kernel parameters file for Raspberry Pi boards.
As systemd-oomd worked in Ubuntu 22.10 (Kinetic) without the need of set this kernel parameter the only conclusion I've reached is that this cgroup has been disabled in a point between kernel 5.19 (kinetic) and kernel 6.2 (lunar) releases.
So I've searched the Raspberry Pi kernel commits related and found this one:
https:/ /github. com/raspberrypi /linux/ commit/ 28aec65bb1743c9 bfa53b036999f98 35c889704e
cgroup: Disable cgroup "memory" by default enable= memory
Some Raspberry Pis have limited RAM and most users won't use the
cgroup memory support so it is disabled by default. Enable with:
cgroup_
At this point I don't know what team should fix this bug. I've updated it for linux-raspi package.