Bug 1809408 - Failed to start Early OOM Daemon.
Summary: Failed to start Early OOM Daemon.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: earlyoom
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vitaly
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1809407
TreeView+ depends on / blocked
 
Reported: 2020-03-03 05:04 UTC by Chris Murphy
Modified: 2020-03-04 21:31 UTC (History)
1 user (show)

Fixed In Version: earlyoom-1.4-2.fc31
Clone Of:
Environment:
Last Closed: 2020-03-04 21:31:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rfjakob earlyoom issues 166 0 None open 1.4 does not respect $PREFIX 2020-03-03 08:57:54 UTC

Description Chris Murphy 2020-03-03 05:04:29 UTC
Description of problem:

After upgrading and rebooting, earlyoom fails to start.


Version-Release number of selected component (if applicable):
earlyoom-1.4-1.fc32.x86_64


How reproducible:
Always, baremetal and VM, Fedora 32 (and 31)


Steps to Reproduce:
1. Update to 1.4, is working OK
2. Reboot
3.

Actual results:

Fails to start during startup.


Expected results:

Should start automatically without error.


Additional info:

$ systemctl status earlyoom
● earlyoom.service - Early OOM Daemon
     Loaded: loaded (/usr/lib/systemd/system/earlyoom.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2020-03-02 22:03:22 MST; 5s ago
       Docs: man:earlyoom(1)
             https://github.com/rfjakob/earlyoom
    Process: 1651 ExecStart=/usr/local/bin/earlyoom $EARLYOOM_ARGS (code=exited, status=203/EXEC)
   Main PID: 1651 (code=exited, status=203/EXEC)
        CPU: 17ms

Mar 02 22:03:22 fmac.local systemd[1]: earlyoom.service: Scheduled restart job, restart counter is at 5.
Mar 02 22:03:22 fmac.local systemd[1]: Stopped Early OOM Daemon.
Mar 02 22:03:22 fmac.local systemd[1]: earlyoom.service: Start request repeated too quickly.
Mar 02 22:03:22 fmac.local systemd[1]: earlyoom.service: Failed with result 'exit-code'.
Mar 02 22:03:22 fmac.local systemd[1]: Failed to start Early OOM Daemon.

Comment 1 Chris Murphy 2020-03-03 05:05:49 UTC
[    6.756236] fmac.local systemd[874]: earlyoom.service: Failed at step EXEC spawning /usr/local/bin/earlyoom: No such file or directory

Comment 2 Chris Murphy 2020-03-03 05:07:33 UTC
$ sudo find /usr -name earlyoom
/usr/bin/earlyoom
/usr/share/doc/earlyoom
/usr/share/licenses/earlyoom

$ cat /usr/lib/systemd/system/earlyoom.service
[Unit]
Description=Early OOM Daemon
Documentation=man:earlyoom(1) https://github.com/rfjakob/earlyoom

[Service]
EnvironmentFile=-/etc/default/earlyoom
ExecStart=/usr/local/bin/earlyoom $EARLYOOM_ARGS
# Run as an unprivileged user with random user id
DynamicUser=true
# Allow killing processes and calling mlockall()
AmbientCapabilities=CAP_KILL CAP_IPC_LOCK
# We don't need write access anywhere
ProtectSystem=strict
# We don't need /home at all, make it inaccessible
ProtectHome=true
# earlyoom never exits on it's own, so have systemd
# restart it should it get killed for some reason.
Restart=always

[Install]
WantedBy=multi-user.target
]$

Comment 3 Vitaly 2020-03-03 08:57:55 UTC
Yes, upstream does not respect $PREFIX now. Reported bug. Will fix it with patch later.

Comment 4 Fedora Update System 2020-03-03 20:28:09 UTC
earlyoom-1.4-2.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4820400ce8

Comment 5 Fedora Update System 2020-03-04 21:31:16 UTC
earlyoom-1.4-2.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.