[systemd-bugs] [Bug 89145] New: Failed at step CGROUP spawning /usr/lib/systemd/systemd

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 89145
           Summary: Failed at step CGROUP spawning
                    /usr/lib/systemd/systemd
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: dh.herrmann at gmail.com
        QA Contact: systemd-bugs at lists.freedesktop.org

I occasionally see this:
  "Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or
directory"

I cannot reproduce this reliably, so I haven't been able to figure out what
exactly is going wrong. I'll try to add some debug-statements, but so far this
is the only information I have:

 - It fails in src/core/execute.c, in exec_child()
 - I only see it on `systemd --user`
 - It only happens for user 'gdm'
 - I suspect it's related to cgroup-delegation (line ~1500), as it only fails
for `systemd --user`

I don't have much insight in systemd CGROUP handling, so if anyone has ideas
where do start debugging, let me know. I'll try to strace PID1 and trigger the
bug, but I haven't succeeded so far.

Thanks
David



Sat 2015-02-14 15:09:50.522160 CET
[s=31993b48a4114763b7f3465695087218;i=10a4c;b=6f35b05bd0c247a58fb97a9befd3e954;m=dd43258;t=50f0ce809a20b;x=a2e3c5b3ea64e49b]
    _UID=0
    _GID=0
    _MACHINE_ID=XXX
    _HOSTNAME=XXX
    SYSLOG_FACILITY=3
    SYSLOG_IDENTIFIER=systemd
    _TRANSPORT=journal
    _CAP_EFFECTIVE=3fffffffff
    _SYSTEMD_CGROUP=/
    PRIORITY=3
    _COMM=(systemd)
    CODE_FILE=src/core/execute.c
    CODE_LINE=1894
    CODE_FUNCTION=exec_spawn
    USER_UNIT=user at 120.service
    MESSAGE_ID=641257651c1b4ec9a8624d7a40a9e1e7
    EXECUTABLE=/usr/lib/systemd/systemd
    MESSAGE=Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such
file or directory
    ERRNO=2
    _BOOT_ID=6f35b05bd0c247a58fb97a9befd3e954
    _PID=1310
    _SOURCE_REALTIME_TIMESTAMP=1423922990522160

-- 
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/20150214/92fea08d/attachment.html>