After updating to lxc-0.8.0-rc3, I'm seeing the behavior of lxc is unchanged.

$ dpkg -l | grep lxc
ii  lxc                                  0.8.0~rc1-3                      Linux 
Containers userspace tools
ii  lxc-dbg                              0.8.0~rc1-3                      Linux 
Containers userspace tools (debug)
ii  lxc-dev                              0.8.0~rc1-3                      Linux 
Containers userspace tools (development)

# 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 tools continue to 'lose' their ability to see liblxc.so.0 after 
attempting to start LXC.

$ ldd `which lxc-console`
        linux-vdso.so.1 =>  (0x00007fff2a7b0000)
        liblxc.so.0 => not found
        libcap.so.2 => /lib/libcap.so.2 (0x00007fd837daf000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd837a27000)
        libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007fd837823000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fd837fdb000)

Yet, containers set to autoload at boot run without problems, and I can use 
lxc-console to connect to their running consoles -- at least, I can do so until 
I try to start a container using 'lxc-start.'

On Mar 10, 2012, at 2:06 AM, Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the lxc package:
> 
> #663274: lxc: Can't start containers.
> 
> It has been closed by Daniel Baumann 
> <daniel.baum...@progress-technologies.net>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Daniel Baumann 
> <daniel.baum...@progress-technologies.net> by
> replying to this email.
> 
> 
> -- 
> 663274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663274
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 
> From: Daniel Baumann <daniel.baum...@progress-technologies.net>
> Subject: Bug#663274: fixed in lxc 0.8.0~rc1-3
> Date: March 10, 2012 2:02:37 AM MST
> To: 663274-cl...@bugs.debian.org
> 
> 
> Format: 1.8
> Date: Sat, 10 Mar 2012 09:51:28 +0100
> Source: lxc
> Binary: lxc lxc-dbg lxc-dev
> Architecture: source i386
> Version: 0.8.0~rc1-3
> Distribution: unstable
> Urgency: low
> Maintainer: Daniel Baumann <daniel.baum...@progress-technologies.net>
> Changed-By: Daniel Baumann <daniel.baum...@progress-technologies.net>
> Description: 
> lxc        - Linux Containers userspace tools
> lxc-dbg    - Linux Containers userspace tools (debug)
> lxc-dev    - Linux Containers userspace tools (development)
> Closes: 663274
> Changes: 
> lxc (0.8.0~rc1-3) unstable; urgency=low
> .
>    * Adding pre-depends to multiarch-support (Closes: #663274).
>    * Updating lintian overrides.
> Checksums-Sha1: 
> cadaee224a3cc01f38d6e2100c355f02ff75446c 1260 lxc_0.8.0~rc1-3.dsc
> 84f91433f94cbbe22d13369540a4db53d3804fdf 45812 lxc_0.8.0~rc1-3.debian.tar.gz
> 36e80787d146aebfee8d4b600ff9dbcd5d94225e 196886 lxc_0.8.0~rc1-3_i386.deb
> 85f5e73600df7631cdd072e3042907863a00b6d1 215494 lxc-dbg_0.8.0~rc1-3_i386.deb
> 5badfe31b5968b9756aabc06059aae35c1ac4704 19926 lxc-dev_0.8.0~rc1-3_i386.deb
> Checksums-Sha256: 
> 4d74bd7b6b92049374518e38245b5535eb8cafb981c556ba843bc989fca0faaa 1260 
> lxc_0.8.0~rc1-3.dsc
> 96ee9b7b7318cfc23efec071202b52c4a3fd48642999f95f982b58e35993fe79 45812 
> lxc_0.8.0~rc1-3.debian.tar.gz
> 02fc78a5fd0283a709a7bd165c47a7d23f47a09f8c1de8586b0219935034e35e 196886 
> lxc_0.8.0~rc1-3_i386.deb
> b5e5866d318fdeb0a80d2e88e23e2ef6719ef171c127c05de78863dbbb9b1c28 215494 
> lxc-dbg_0.8.0~rc1-3_i386.deb
> ef7d47013c30147345a2db3a5d2fc05aaf450cb4ee91f49366b1c696823d558d 19926 
> lxc-dev_0.8.0~rc1-3_i386.deb
> Files: 
> f45513dd72b0b524bb0ed22a1f39c317 1260 admin optional lxc_0.8.0~rc1-3.dsc
> b10226515f2e09c4ba47d6ca74cd3d03 45812 admin optional 
> lxc_0.8.0~rc1-3.debian.tar.gz
> 368b32ddec9f4447c79ecca374c2dd8c 196886 admin optional 
> lxc_0.8.0~rc1-3_i386.deb
> 21cfe8462d06e3f757005f7549d0aca2 215494 debug extra 
> lxc-dbg_0.8.0~rc1-3_i386.deb
> ee853cbf48edb9674c71e73bcf89a967 19926 libdevel optional 
> lxc-dev_0.8.0~rc1-3_i386.deb
> 
> 
> 
> 
> From: Troy Telford <ttelford.gro...@gmail.com>
> Subject: lxc: Can't start containers.
> Date: March 9, 2012 5:38:16 PM MST
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> 
> 
> 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
> 
> 
> 
> 

--
Troy Telford
ttelford.gro...@gmail.com

Reply via email to