[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

After updating to the latest packages, this issue is solve. I can lxc-
start, lxc-attach, lxc-stop, and lxc-execute.

I do get some warning/error spew when running lxc-execute though. If
this looks unexpected, I can open a separate bug for it:

$ lxc-execute -n t1 -- /bin/bash
lxc-execute: utils.c: safe_mount: 1691 Invalid argument - Failed to mount 
/sys/kernel/debug onto /usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug
lxc-execute: utils.c: safe_mount: 1691 Device or resource busy - Failed to 
mount mqueue onto /usr/lib/x86_64-linux-gnu/lxc/dev/mqueue
init.lxc.static: initutils.c: mount_fs: 36 failed to mount /proc : Device or 
resource busy
init.lxc.static: initutils.c: mount_fs: 36 failed to mount /dev/mqueue : Device 
or resource busy

The first two of those show up in the container log file upon lxc-start
too:

lxc-start 20160316211700.325 ERRORlxc_utils - utils.c:safe_mount:1691 - 
Invalid argument - Failed to mount /sys/kernel/debug onto 
/usr/lib/x86_64-linux-gnu/lxc/sys/kernel/debug
lxc-start 20160316211700.325 ERRORlxc_utils - utils.c:safe_mount:1691 - 
Device or resource busy - Failed to mount mqueue onto 
/usr/lib/x86_64-linux-gnu/lxc/dev/mqueue

Thanks very much for fix and bug comments; this has been one of the most
productive bug reports I've ever filed:-)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

** Changed in: lxc (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

The EBUSY errors from lxc-init mounts are ok, it's because lxc has
already mounted those (by following the automatically included
configuration files).

i'd expect eperm for the /sys/kernel/debug mount, because you're not
allowed to read under /sys/kernel/debug.  But strace shows that by hand
i also get einval.  So nothing here is unexpected or (so long as it
doesn't break anything for you) needing a bug.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Launchpad Bug Tracker]

This bug was fixed in the package lxcfs - 2.0.0~rc5-0ubuntu1

---
lxcfs (2.0.0~rc5-0ubuntu1) xenial; urgency=medium

  * Merge next upstream rc
  * This fixes a bug where sudo would mis-chown a user's systemd cgroup
(LP: #1556447)
  * Drop upstream paches which are in this rc

 -- Serge Hallyn   Mon, 14 Mar 2016 16:09:50
-0700

** Changed in: lxcfs (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Thanks. The chown solves the issue. I didn't need to make the
modification to the pam config file at all. I do need to do the chown
every time I log in though, with or without the pam change.

FWIW, when I ssh into the working server, the relevant /sys directory is
owned by swarren:swarren without any intervention. On my laptop, it's
always owned by root:root.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

Quoting Stephen Warren (swar...@wwwdotorg.org):
> Could you please expand on "Then re-chown your current systemd cgroup"?
> I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
> path I should chown.

The systemd cgroupfs is mounted under /sys/fs/cgroup/systemd.  Your current
login path can be found with

awk -F: '/systemd/ { print $3 }' /proc/self/cgroup

so

pwd=/sys/fs/cgroup/systemd/`awk -F: '/systemd/ { print $3 }' /proc/self/cgroup`
sudo -E chown $(id -u):$(id -g) $pwd

should work

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Could you please expand on "Then re-chown your current systemd cgroup"?
I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
path I should chown.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

Thanks,  Stephen, culprit found.  The systemd cgroup was yours - until
you did a sudo.

For now you can work around this by commenting out the libpam-cgfs line
from /etc/pam.d/common-session-noninteractive.  Then re-chown your
current systemd cgroup to yourself or log back in.

I'm not yet sure whether the proper fix will be to

1. remove the line from noninteractive,
2. have libpam-cgfs check for user-$loginuid.slice in the current systemd 
cgroup, and create a new one if it doesn't match
3. just add another libpam-cgfs argument to say whether to create a new systemd 
cgroup, and have it not do so for noninteractive.


** Changed in: lxc (Ubuntu)
   Importance: Undecided => High

** Also affects: lxcfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lxcfs (Ubuntu)
   Importance: Undecided => High

** Changed in: lxcfs (Ubuntu)
   Status: New => Triaged

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Yes, I'm running lightdm.

$ cat /etc/pam.d/common-session 
session [default=1] pam_permit.so
session requisite   pam_deny.so
session requiredpam_permit.so
session optionalpam_umask.so
session requiredpam_unix.so 
session optionalpam_systemd.so 
session optionalpam_cgfs.so -c freezer,memory,name=systemd

(comments all stripped for brevity

That file should be unmodified relative to the package defaults, or put
another way, I haven't fiddled with it.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Launchpad Bug Tracker]

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

** Changed in: lxc (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Evgeni Golov]

Hi,

I am seeing this on an up2date VM of 16.04, logging in via SSH. libpam-
cgfs is installed.

Error output from the log:
  lxc-start 20160313140655.936 ERRORlxc_cgfsng - 
cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found
  lxc-start 20160313140655.936 ERRORlxc_start - start.c:lxc_spawn:1036 
- failed initializing cgroup support
  lxc-start 20160313140655.936 ERRORlxc_start - 
start.c:__lxc_start:1286 - failed to spawn 'user1'

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Serge Hallyn]

Do you know whether you are using lightdm?  Can you show your
/etc/pamd.d/common-session file?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1556447] Re: lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no systemd controller mountpoint found

[Stephen Warren]

I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems the same way w.r.t. lxc (e.g. /etc/subuid, /etx/lxc/lxc-
usernet, ~/.config/lxc/default.conf, etc.). The primary difference is
that the Linode system is running a Linode-provided kernel, whereas my
laptop is running an Ubuntu-provided kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1556447

Title:
  lxc-start fails: lxc_cgfsng - cgfsng.c:all_controllers_found:430 - no
  systemd controller mountpoint found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556447/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs