Your message dated Fri, 29 Jun 2012 23:40:10 +0200
with message-id <[email protected]>
and subject line Re: some containers in some situations/setups cannot be started
has caused the Debian Bug report #663274,
regarding some contains in some situations/setups cannot be started
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
663274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663274
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 0.8.0~rc1-2
Severity: important
This is probably related to #663062, possibly a dup.
I haven't rebooted my system in a few months, so I haven't noticed this until
now:
Prior to the reboot, I was using kernel 3.2.0-1-amd64, post-reboot is
3.2.0-2-amd64 (I've done several boots since; the kernel version doesn't seem
to matter)
I run a sid machine, and am using the 'latest' version of LXC available (was
0.7.5-24 until this afternoon, when it bumped to 0.8.0~rc1-2, I believe)
I have several "known good" containers; some auto-launch at boot, others are
manually started.
The auto-launched containers run fine, however I'm entirely unable to load the
containers manually:
With yesterday's lxc package:
$ lxc-start -n radius
lxc-start: Invalid argument - pivot_root syscall failed
lxc-start: failed to setup pivot root
lxc-start: failed to set rootfs for 'radius'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'radius'
lxc-start: Device or resource busy - failed to remove cgroup
'/sys/fs/cgroup//lxc/radius'
And with 0.8.0-rc1-2:
lxc-start -n mumble
lxc-start: Invalid argument - pivot_root syscall failed
lxc-start: failed to setup pivot root
lxc-start: failed to set rootfs for 'mumble'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'mumble'
Interestingly enough, I also have a problem with other LXC tools:
After a fresh reboot, if I use 'lxc-console' on an auto-started (running)
container, it works as expected.
HOWEVER...
After I attempt (and fail) to start a container manually (using lxc-start [-d]
-n <name>), lxc-console shows:
lxc-console: error while loading shared libraries: liblxc.so.0: cannot open
shared object file: No such file or directory
lxc-console does exist:
/usr/lib/lxc/liblxc.so.0 -> /usr/lib/lxc/liblxc.so.0.7.5 (it's a valid symlink;
/usr/ib/lxc/liblxc.so.0.7.5 also exists).
But...
# ldd $(which lxc-console)
linux-vdso.so.1 => (0x00007fffbddff000)
liblxc.so.0 => not found
libcap.so.2 => /lib/libcap.so.2 (0x00007fc101132000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc100daa000)
libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007fc100ba6000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc10135e000)
I have to admit: I'm a bit WTF'd out by the way liblxc 'vanishes' as far as
lxc-console (and other lxc tools). I'm not sure (yet) if I have to reboot, or
reinstall lxc to get liblxc to be located by the linker.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-27
ii libcap2 1:2.22-1
Versions of packages lxc recommends:
ii debootstrap 1.0.38
ii libcap2-bin 1:2.22-1
Versions of packages lxc suggests:
ii lxctl 0.3.1+debian-1
-- debconf information:
lxc/directory: /var/lib/lxc
lxc/title:
lxc/auto: true
lxc/shutdown: stop
--- End Message ---
--- Begin Message ---
Version: 0.8.0~rc1-5
this has been fixed with the patch for #664764, closing.
--
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: [email protected]
Internet: http://people.progress-technologies.net/~daniel.baumann/
--- End Message ---
