#1110567 low-memory-monitor.service immediatly fails

Package:
low-memory-monitor
Source:
low-memory-monitor
Description:
Monitors low-memory conditions
Submitter:
Tareeq Ali
Date:
2025-08-08 20:49:03 UTC
Severity:
normal
#1110567#5
Date:
2025-08-08 20:47:23 UTC
From:
To:
Dear Maintainer,


   * What led up to the situation?
        On boot I see low-memory-monitor.service fails to start. systemctl
status low-memory-monitor.service fails to start.
        I see the following errors doing journalctl -u low-memory-
monitor.service;
_____
Mar 07 09:02:49 darthvader systemd[1]: Started low-memory-monitor.service - Low
Memory Monitor.
Mar 07 09:02:49 darthvader (-monitor)[1612]: low-memory-monitor.service: Failed
to set up CPU scheduling: Operation not permitted
Mar 07 09:02:49 darthvader (-monitor)[1612]: low-memory-monitor.service: Failed
at step SETSCHEDULER spawning /usr/libexec/low-memory-monitor: Operation not
permitted
Mar 07 09:02:49 darthvader systemd[1]: low-memory-monitor.service: Main process
exited, code=exited, status=214/SETSCHEDULER
Mar 07 09:02:49 darthvader systemd[1]: low-memory-monitor.service: Failed with
result 'exit-code'.
____

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        I am able to start the service if I modify /usr/lib/systemd/system/low-
memory-monitor.service and edit lines 12-13 by hashing them;


#CPUSchedulingPolicy=fifo
#CPUSchedulingPriority=1

   * What was the outcome of this action?
        This gets the service to start properly, but unsure of the consequences
of not changing cpu scheduling policy or scheduling priority.