Installation of cgmanager prevents booting with systemd

[Harry]

I have a completely upgraded Ubuntu Utopic development branch setup, with proprietary nvidia drivers installed.
I have set my booting system to boot with systemd instead of the upstart one.
The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager.
However, installation of cgmanager (versions 0.26-0ubuntu5 or 0.27-0ubuntu7) leads to a setup, where booting is not completed (with systemd).
Not even tty1 is created and thus gdm (which I use instead of lightdm) is not started.
I have the newest systemd installed (version 204-14ubuntu2).
Booting with upstart, on the other hand, goes just fine.

If I downgrade systemd to version 6-3 (and remove package cgmanager) all is well again and systemd booting is fine again.

[Harry (harry33)]

I noticed that bug LP: #1342586 is solved and fix released, but this new bug is not solved by that systemd update.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Serge Hallyn (serge-hallyn)]

Hi,

the systemd-shim with cgmanager was intended for use with systemd 208 (currently in debian experimental). Can you try building and installing that and see if that fixes it for you? If it does we'll need to tighten the packaging for systemd-shim to rely on the newer systemd. (You may need to edit the libpam-systemd Depends to add systemd-shim as an alternative ot systemd-sysv (to keep upstart working), and also save the old /etc/init/systemd-logind.conf to start systemd for you).

[Serge Hallyn (serge-hallyn)]

I'm building a version of 208 in ppa:serge-hallyn/systemd; I will try to reproduce your issue with that on a utopic desktop vm. Assuming I can reproduce it I should be able to easily figure out the problem.

[Harry (harry33)]

Thank you Serge.
I am afraid the building procedure you asked is beyond my skills.

[Martin Pitt (pitti)]

FTR, I have tested systemd 208 packages in http://people.canonical.com/~pitti/tmp/systemd-208/ for amd64 and armhf.

Note that the newer systemd-shim code itself should not cause any regression at all, as logind 204 does not call it. But starting cgmanager might of course interfere with logind. My system has run fine for several days though (current utopic, logind 204, with upstart), so I can't reproduce this problem.

[Harry (harry33)]

Martin,
you mentioned your system runs fine with upstart (that is booting with upstart).
However, this bug is about not being able to boot with systemd (init=/lib/systemd/systemd).
Can you reproduce the bug with systemd booting?

[Martin Pitt (pitti)]

Harry [2014-07-20 13:59 -0000]:
> Can you reproduce the bug with systemd booting?

No, that works fine as well, I tested both before I uploaded the new
systemd-shim.

[Anders Kaseorg (andersk)]

I see the same problem booting utopic with systemd and cgmanager. After enabling the debug shell, I found these messages in journalctl:

Jul 20 23:54:03 fixed-disk cgmanager[682]: * Starting cgroup management daemon cgmanager
Jul 20 23:54:03 fixed-disk cgmanager[682]: ...done.
Jul 20 23:54:03 fixed-disk kernel: cgroup: new mount options do not match the existing superblock, will be ignored
Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=cpu, cgroup_path=system/cgmanager.service/control failed: invalid request
Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_remove failed: systemd:system/cgmanager.service did not exist
Jul 20 23:54:03 fixed-disk systemd[1]: Started LSB: Cgroup manager daemon.
Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=systemd, cgroup_path=system/cgmanager.service failed: invalid request
Jul 20 23:54:03 fixed-disk systemd[1]: Failed to check whether cgroup is empty: Resource temporarily unavailable
Jul 20 23:54:03 fixed-disk systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-vconsole-setup.service' for details.
Jul 20 23:54:03 fixed-disk systemd[1]: Starting ACPI event daemon...
Jul 20 23:54:03 fixed-disk systemd[1]: cgmanager: cgm_get for controller=cpu, cgroup_path=system/acpid.service/control failed: invalid request
Jul 20 23:54:03 fixed-disk systemd[1]: Started ACPI event daemon.
Jul 20 23:54:03 fixed-disk systemd[861]: Failed at step CGROUP spawning /usr/sbin/acpid: Operation not permitted
Jul 20 23:54:03 fixed-disk systemd[1]: acpid.service: main process exited, code=exited, status=219/CGROUP
Jul 20 23:54:03 fixed-disk systemd[1]: Unit acpid.service entered failed state.

etc. Lots of other services fail with similar cgm_get errors.

[Anders Kaseorg (andersk)]

This seems to be fixed after upgrading to Martin’s systemd 208 packages.

[Harry (harry33)]

Yes,
I can confirm that the Martin's PPA version of systemd (208-2pitti1) works fine with the latest cgmanager (0.27-0ubuntu7) and with the package cgmanager and latest systemd-shim (6-3ubuntu1) installed.

I think we should get the systemd 208 into the Utopic official repos now.

[Martin Pitt (pitti)]

> No, that works fine as well, I tested both before I uploaded the new systemd-shim.

Sorry, seems I tested the original systemd-shim update without the new cgmanager dependency. It's broken here as well.

[Martin Pitt (pitti)]

This is fixed with the changed cgmanager integration from systemd 208, see bug 1346199. Testing from -proposed and feedback to that bug is highly appreciated!

[Cavsfan (cavsfan)]

I initiated bug https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1344196

It suggested I do this:
sudo apt-get update && sudo apt-get -y dist-upgrade

It pulled in gdb amd64 7.7.1-0ubuntu5.

cavsfan@cavsfan-MS-7529:~$ apt-cache policy systemd
systemd:
  Installed: 204-14ubuntu2
  Candidate: 204-14ubuntu2

cavsfan@cavsfan-MS-7529:~$ apt-cache policy cgmanager
cgmanager:
  Installed: 0.27-0ubuntu7
  Candidate: 0.27-0ubuntu7

I guess systemd 208 fixes this and will that be available in regular updates or just a special ppa? I was just testing systemd because it was available without adding any ppa.

[Cavsfan (cavsfan)]

I enabled Pre-Release updates and got just the following:
libpam-systemd (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2
libsystemd-daemon0 (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2
libsystemd-journal0 (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2
libsystemd-login0 (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2
systemd (version 204-14ubuntu2) will be upgraded to version 208-6ubuntu2

I then disabled Pre-Release updates. I'll reboot with systemd and see if it works.

[Cavsfan (cavsfan)]

208-6ubuntu2 fixed my system. I rebooted and am up and running fine.

[Martin Pitt (pitti)]

Cavsfan [2014-07-23 16:25 -0000]:
> I guess systemd 208 fixes this and will that be available in regular
> updates or just a special ppa? I was just testing systemd because it was
> available without adding any ppa.

It will go into utopic proper, but we are holding it back for some
days, as we need to sort out some problems on the current Ubuntu Touch
images, and we don't want to introduce even more variance there.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 208-6ubuntu2

---------------
systemd (208-6ubuntu2) utopic; urgency=medium

  * Merge some more fixes from master, see 208-7 changelog.
 -- Martin Pitt <email address hidden> Wed, 23 Jul 2014 12:24:42 +0200