Quoting Michael Biebl (bi...@debian.org): Hi Michael,
> Looking at v215, it seems as if starting cgmanager as part of the > installation messes up the running systemd state. When triggering > reboot, (i.e. poking /dev/initctl), I get the following: > > Incoming traffic on systemd-initctl.socket > Trying to enqueue job systemd-initctl.service/start/replace > Installed new job systemd-initctl.service/start as 371 > Enqueued job systemd-initctl.service/start as 371 > systemd-initctl.socket changed listening -> running > Sent message type=signal sender=n/a destination=n/a > object=/org/freedesktop/systemd1/unit/systemd_2dinitctl_2esocket > interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=754 > reply_cookie=0 error=n/a > Sent message type=signal sender=n/a destination=n/a > object=/org/freedesktop/systemd1/unit/systemd_2dinitctl_2esocket > interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=755 > reply_cookie=0 error=n/a > Sent message type=signal sender=n/a destination=n/a > object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager > member=JobNew cookie=756 reply_cookie=0 error=n/a > Received SIGCHLD from PID 1979 (shutdown). > Child 1979 (shutdown) died (code=exited, status=0/SUCCESS) > ^[[1;31mFailed to create cgroup : No such file or directory^[[0m > About to execute: /lib/systemd/systemd-initctl > Forked /lib/systemd/systemd-initctl as 1980 > systemd-initctl.service changed dead -> running > Job systemd-initctl.service/start finished, result=done > Sent message type=signal sender=n/a destination=n/a > object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager > member=JobRemoved cookie=757 reply_cookie=0 error=n/a > ^[[1;31mFailed to create cgroup : No such file or directory^[[0m > Failed to realize cgroups for queued unit user.slice: No such file or > directory > ^[[1;31mFailed to create cgroup : No such file or directory^[[0m > Failed to realize cgroups for queued unit cgmanager.service: No such file or > directory At this point, systemd-shim is installed, right? Has it diverted /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service already? Would that be the actual core of the problem? If so, should systemd-shim recognize that pid 1 is systemd and refuse to run? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
