Bug#760357: lxc: can not start container which used to work after recent system update

2014-09-03 Thread Alex Mestiashvili
Package: lxc
Version: 1:1.0.5-2
Severity: important

that's what I get when I try to start a container:

lxc-start -n sid
lxc-start: No such file or directory - failed to read
/sys/fs/cgroup/lxc/cpuset.cpus
lxc-start: Failed to initialize cpuset for '/lxc' in '/sys/fs/cgroup'.
lxc-start: Device or resource busy - cgroup_rmdir: failed to delete
/sys/fs/cgroup//systemd
lxc-start: Directory not empty - cgroup_rmdir: failed to delete
/sys/fs/cgroup//cgmanager
lxc-start: Device or resource busy - cgroup_rmdir: failed to delete
/sys/fs/cgroup/
lxc-start: failed creating cgroups
lxc-start: failed to spawn 'sid'
lxc-start: The container failed to start.
lxc-start: Additional information can be obtained by setting the --logfile
and --log-priority options.

#mount | grep cgroup
cgroup on /sys/fs/cgroup type cgroup
(rw,relatime,cpuset,cpu,cpuacct,devices,freezer,net_cls,blkio,perf_event)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,size=12k)
systemd on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,name=systemd)

lxc-checkconfig
Kernel configuration found at /boot/config-3.14-2-amd64
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled
Multiple /dev/pts instances: enabled

--- Control groups ---
Cgroup: enabled
Cgroup namespace: required
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled

--- Misc ---
Veth pair device: enabled
Macvlan: enabled
Vlan: enabled
File capabilities: enabled

It seems that for some reason Cgroup namespace is missing.. a kernel issue ?
--- Cgroup namespace: required


cat /proc/cgroups
#subsys_namehierarchy   num_cgroups enabled
cpuset  2   1   1
cpu 2   1   1
cpuacct 2   1   1
memory  0   1   0
devices 2   1   1
freezer 2   1   1


net_cls 2   1   1


blkio   2   1   1
perf_event  2   1   1


dpkg -l | egrep (cgroup|cgmanager|lxc)
ii  cgmanager  0.30-1
  amd64Central cgroup manager daemon
ii  cgroup-bin 0.41-5
  all  control and monitor control groups (transitional package)
ii  cgroup-tools   0.41-5
  amd64control and monitor control groups (tools)
ii  cgroupfs-mount 1.0
   all  Light-weight package to set up cgroupfs mounts
ii  libcgmanager0:amd640.30-1
  amd64Central cgroup manager daemon (client library)
ii  libcgroup1:amd64   0.41-5
  amd64control and monitor control groups (library)
ii  lxc1:1.0.5-2
   amd64Linux Containers userspace tools
ii  lxc-stuff  1.0.4-3
   all  Linux Containers userspace tools (additional utilities)


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lxc depends on:
ii  init-system-helpers  1.21
ii  libapparmor1 2.8.0-5.1+b2
ii  libc62.19-10
ii  libcap2  1:2.24-4
ii  libseccomp2  2.1.1-1
ii  libselinux1  2.3-1
ii  multiarch-support2.19-10
ii  python3  3.4.1-1

Versions of packages lxc recommends:
ii  lua5.2  5.2.3-1
ii  rsync   3.1.1-2

Versions of packages lxc suggests:
ii  debootstrap  1.0.60

-- debconf information:
* lxc/directory: /var/lib/lxc
  lxc/auto: true
  lxc/shutdown: /usr/bin/lxc-halt
  lxc/title:


Bug#760357: lxc: can not start container which used to work after recent system update

2014-09-03 Thread Daniel Baumann
severity 760357 normal
tag 760357 unreproducible
tag 760357 moreinfo
thanks

Hi,

i'm running lxc 1.0.5-2 and systemd 208-8 here, on sid with kernel
3.14-2-amd64.

creating/starting/stopping containers created with lxc-create -t debian
works flawlessly, so your problem is a local problem.

On 09/03/2014 10:12 AM, Alex Mestiashvili wrote:
 lxc-start -n sid
 lxc-start: No such file or directory - failed to read
 /sys/fs/cgroup/lxc/cpuset.cpus
 lxc-start: Failed to initialize cpuset for '/lxc' in '/sys/fs/cgroup'.
 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete
 /sys/fs/cgroup//systemd
 lxc-start: Directory not empty - cgroup_rmdir: failed to delete
 /sys/fs/cgroup//cgmanager
 lxc-start: Device or resource busy - cgroup_rmdir: failed to delete
 /sys/fs/cgroup/
 lxc-start: failed creating cgroups
 lxc-start: failed to spawn 'sid'
 lxc-start: The container failed to start.
 lxc-start: Additional information can be obtained by setting the
 --logfile and --log-priority options.

please do so by calling your lxc-start with debug logs enabled.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#760357: lxc: can not start container which used to work after recent system update

2014-09-03 Thread Alex Mestiashvili
It seems that the problem was caused by  cgroup mount defined in fstab.
This configuration worked fine with  3.12 ( just rebooted and tested -
container started).
Currently I commented out cgroup in fstab and after reboot everything works
fine.
I also see cgmanager process and cgroup mounts.

Sorry for the noise.
Alex


Bug#760357: lxc: can not start container which used to work after recent system update

2014-09-03 Thread Daniel Baumann

On 09/03/2014 01:51 PM, Alex Mestiashvili wrote:

It seems that the problem was caused by  cgroup mount defined in fstab.


well, yes.. if you use systemd, you shoudn't mount it through fstab.

since this is probably going to be a quite common case since we had to 
instruct people to write it in fstab (eventhough #601757 was filled 
years ago to make sysvinit mount it)..


..i'll add a preinst check to give out a warning about that.

--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org