I've generated a sosreport, but its 7.7G. How would you like me to get this to you?
The interesting part is that all this was deployed via juju, so I don't know how we got into this state. It also appears to be the only node in this state, so its a bit confusing as to how it got to be this way. Is there anything I can check configuration wise to see why its using deputy systemd? Its certainly not something we've explicitly picked as far as I know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error Status in systemd package in Ubuntu: Confirmed Bug description: After rebooting a KVM instance hosting LXCs, we get the following error: $ sudo lxc-ls --fancy lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request and the LXCs won't start up. In the error logs it showed: lxc-start 1487906073.534 ERROR lxc_cgfs - cgfs.c:lxc_cgroupfs_create:873 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup. The only way I could get the lxcs started was to stop and start cgmanager, just a simple restart wasn't sufficient. Please let me know if you need any further information. $ lsb_release -a Description: Ubuntu 14.04.5 LTS Release: 14.04 $ dpkg-query -W systemd systemd 204-5ubuntu20.24 $ dpkg-query -W cgmanager cgmanager 0.24-0ubuntu7.5 $ dpkg-query -W lxc lxc 1.0.9-0ubuntu2 $ uname -a Linux infra 3.13.0-110-generic #157-Ubuntu SMP Mon Feb 20 11:54:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
