Your message dated Wed, 14 Sep 2016 06:57:12 -0700
with message-id <[email protected]>
and subject line Re: Bug#837743: lxc: Segfault (symbol size mismatch) when
starting container created with "download" template
has caused the Debian Bug report #837743,
regarding lxc: Segfault (symbol size mismatch) when starting container created
with "download" template
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.)
--
837743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837743
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:2.0.4-1
Severity: important
I created an unpriviliged Ubuntu (xenial, amd64) container using "lxc-create -n
foo -t download", and it seemed to complete with no problems. But when I try to
start this container using "lxc-start -n foo", I get this error:
>lxc-start: Symbol `ns_info' has different size in shared object, consider
>re-linking
>Segmentation fault
Lxc doesn't provide any more logging information or output, even when I set
--logpriority to something high. I also tried creating a Debian (sid, amd64)
container using the download template and got the same error.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-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
Init: systemd (via /run/systemd/system)
Versions of packages lxc depends on:
ii init-system-helpers 1.44
ii libapparmor1 2.10.95-4
ii libc6 2.24-2
ii libcap2 1:2.25-1
ii liblxc1 1:2.0.4-1
ii libseccomp2 2.3.1-2
ii libselinux1 2.5-3
ii python3 3.5.1-4
pn python3:any <none>
Versions of packages lxc recommends:
ii bridge-utils 1.5-9
ii cgmanager 0.41-2
ii debootstrap 1.0.83
ii dirmngr 2.1.15-2
ii dnsmasq-base 2.76-4
ii gnupg 2.1.15-2
ii iptables 1.6.0-3
ii libpam-cgfs 2.0.3-1
ii lxcfs 2.0.3-1
ii openssl 1.0.2h-1
ii rsync 3.1.1-3
ii uidmap 1:4.2-3.1
Versions of packages lxc suggests:
ii apparmor 2.10.95-4
pn btrfs-tools <none>
pn lua5.2 <none>
pn lvm2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
> On Sep 14, 2016, at 05:58, Evgeni Golov <[email protected]> wrote:
>
> Hi,
>
> On Wed, Sep 14, 2016 at 03:32:28AM -0700, Michael Gardner wrote:
>> Thanks for looking into this.
>>
>> How can I debug further? LXC isn't giving me much to go on, so I'm at a loss.
>
> Well, as every segfault, gdb, but that's pain.
>
> Can you please provide the output of the following?
> which lxc-start
> ldd $(which lxc-start)
> dpkg -l |grep lxc
>
> I suspect that you somehow have a broken/old liblxc somewhere.
Ah, you are right of course. There was another version of lxc lurking in my
$PATH; apparently I'd had to compile it manually some time ago.
Thanks, and sorry for the noise.
--- End Message ---
