Bug 1880882

Summary: earlyoom fails to start with systemd-245.8-1
Product: [Fedora] Fedora Reporter: Tom Seewald <tseewald>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: fedoraproject, filbranden, flepied, h.reindl, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek, z
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-245.8-2.fc32 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-23 17:12:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Journal of boot where earlyoom fails to start none

Description Tom Seewald 2020-09-21 01:35:46 UTC
Created attachment 1715480 [details]
Journal of boot where earlyoom fails to start

Description of problem:

The earlyoom service fails to start after upgrading to systemd-245.8-1.fc32.x86_64 (from systemd-245.7-1.fc32.x86_64). It reports that earlyoom exited with "status=213/SECUREBITS".


Version-Release number of selected component (if applicable):

systemd-245.8-1.fc32.x86_64
earlyoom-1.6.1-1.fc32.x86_64


How reproducible:

Always.


Steps to Reproduce:

1. Upgrade to systemd-245.8-1.fc32.x86_64
2. Reboot
3. Examine the output of "systemctl status earlyoom.service"


Actual results:

Early OOM fails to start.

# systemctl status earlyoom.service
● earlyoom.service - Early OOM Daemon
    Loaded: loaded (/usr/lib/systemd/system/earlyoom.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Sun 2020-09-20 20:07:24 CDT; 5min ago
    Docs: man:earlyoom(1)
            https://github.com/rfjakob/earlyoom
Main PID: 858 (code=exited, status=213/SECUREBITS)
        CPU: 7ms

Sep 20 20:07:24 tom-desktop systemd[1]: earlyoom.service: Main process exited, code=exited, status=213/SECUREBITS
Sep 20 20:07:24 tom-desktop systemd[1]: earlyoom.service: Failed with result 'exit-code'.
Sep 20 20:07:24 tom-desktop systemd[1]: earlyoom.service: Scheduled restart job, restart counter is at 5.
Sep 20 20:07:24 tom-desktop systemd[1]: Stopped Early OOM Daemon.
Sep 20 20:07:24 tom-desktop systemd[1]: earlyoom.service: Start request repeated too quickly.
Sep 20 20:07:24 tom-desktop systemd[1]: earlyoom.service: Failed with result 'exit-code'.
Sep 20 20:07:24 tom-desktop systemd[1]: Failed to start Early OOM Daemon.


Expected results:

Early OOM starts and continues to run.

# systemctl status earlyoom.service
● earlyoom.service - Early OOM Daemon
     Loaded: loaded (/usr/lib/systemd/system/earlyoom.service; enabled; vendor preset: disabled)
     Active: active (running) since Sun 2020-09-20 20:18:36 CDT; 54s ago
       Docs: man:earlyoom(1)
             https://github.com/rfjakob/earlyoom
   Main PID: 785 (earlyoom)
      Tasks: 1 (limit: 10)
     Memory: 1.4M (max: 50.0M)
        CPU: 17ms
     CGroup: /system.slice/earlyoom.service
             └─785 /usr/bin/earlyoom -r 0 -m 4 -M 409600 --prefer ^Web Content$ --avoid ^(dnf|packagekitd|gnome-shell|gnome-session-c|gnome-session-b|lightdm|sddm|sddm-helper>

Sep 20 20:18:36 tom-desktop systemd[1]: Started Early OOM Daemon.
Sep 20 20:18:36 tom-desktop earlyoom[785]: earlyoom 1.6.1
Sep 20 20:18:36 tom-desktop earlyoom[785]: Preferring to kill process names that match regex '^Web Content$'
Sep 20 20:18:36 tom-desktop earlyoom[785]: Will avoid killing process names that match regex '^(dnf|packagekitd|gnome-shell|gnome-session-c|gnome-session-b|lightdm|sddm|sddm->
Sep 20 20:18:36 tom-desktop earlyoom[785]: mem total: 23800 MiB, swap total: 12059 MiB
Sep 20 20:18:36 tom-desktop earlyoom[785]: sending SIGTERM when mem <=  1.68% and swap <= 10.00%,
Sep 20 20:18:36 tom-desktop earlyoom[785]:         SIGKILL when mem <=  0.84% and swap <=  5.00%


Additional info:

After rolling back to systemd-245.7-1, the earlyoom service starts without issue.

See the attached journal for the full context of the errors.

Comment 1 Fedora Update System 2020-09-21 08:01:16 UTC
FEDORA-2020-0d29e88946 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d29e88946

Comment 2 Fedora Update System 2020-09-21 08:01:32 UTC
FEDORA-2020-0d29e88946 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d29e88946

Comment 3 Zbigniew Jędrzejewski-Szmek 2020-09-21 13:56:46 UTC
*** Bug 1880989 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2020-09-21 14:28:33 UTC
FEDORA-2020-0d29e88946 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0d29e88946`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d29e88946

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Tom Seewald 2020-09-21 19:59:50 UTC
Upgrading to systemd-245.8-2.fc32 appears to resolve this.

Comment 6 Fedora Update System 2020-09-23 17:12:55 UTC
FEDORA-2020-0d29e88946 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.