[systemd-bugs] [Bug 88996] New: systemd is ended by oom killer if MemoryLimit is exhausted.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 5 05:44:11 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88996

            Bug ID: 88996
           Summary: systemd is ended by oom killer if MemoryLimit is
                    exhausted.
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: alexander.haensch at ipc.uni-tuebingen.de
        QA Contact: systemd-bugs at lists.freedesktop.org

I think this issue supports systemd-critics a lot and it should be fixed.
Adding the following lines to a systemd unit can cause a termination of the
systemd service, which leads to unclean shutdown of the system.

[Service]
MemoryAccounting=True
MemoryLimit=1G

The reason is that the MemoryLimit is per default added to the system slice.
This should not be the default behavior as a simple badly written script can
exhaust the given limit and the swap. The consequence is a not responsible
systemd.

A) systemd should have its own slice, so that memory restictions can not bring
systemd down.
B) per default, units should not add to the system slice.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150205/4d9c76f0/attachment.html>


More information about the systemd-bugs mailing list