[Lxc-users] errors

Tamas Papp tompos at martos.bme.hu
Wed May 22 23:46:54 UTC 2013


On 05/23/2013 01:36 AM, Tamas Papp wrote:
> On 05/23/2013 01:02 AM, Tamas Papp wrote:
>> hi All,
>>
>> # lxc-ls --fancy
>> Traceback (most recent call last):
>>      File "/usr/bin/lxc-ls", line 221, in <module>
>>        ips = container.get_ips(protocol=protocol, timeout=1)
>> TypeError: 'protocol' is an invalid keyword argument for this function
>>
>>
>> # lxc-info -n sc --state-is=running
>> # echo $?
>> 1
>>
>> The container is running.
>>
>> ii  lxc 0.9.0.0~staging~20130521-1727-0ubuntu1~ppa1~pre Linux Containers userspace tools
>>
>> # lsb_release -a
>> No LSB modules are available.
>> Distributor ID:    Ubuntu
>> Description:    Ubuntu 12.04.2 LTS
>> Release:    12.04
>> Codename:    precise
>>
>> Linux virt102 3.2.0-43-generic #68-Ubuntu SMP Wed May 15 03:33:33 UTC 2013 x86_64 x86_64 x86_64
>> GNU/Linux
>>
>>
>>
>> I'm not sure, it's related, but the server is after a restart, because lxc-* commands were segfaulting.
>>
>> Do you have an idea?
> I downgraded to 0.9.0.0~staging~20130516-1655-0ubuntu1~ppa1~precise1, segfault.
> Then reboot and now it's stuck at this stage:
>
> Process 77488 detached
> <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 77488
> --- SIGCHLD (Child exited) @ 0 (0) ---
> fstat(3, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
> lseek(3, 0, SEEK_CUR)                   = -1 ESPIPE (Illegal seek)
> read(3, "", 6)                          = 0
> close(3)                                = 0
> geteuid()                               = 0
> open("/dev/shm/sem.lxcapi.bioreg-vmc01", O_RDWR|O_NOFOLLOW) = 3
> fstat(3, {st_mode=S_IFREG|0640, st_size=32, ...}) = 0
> mmap(NULL, 32, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0x7fe5c5fce000
> close(3)                                = 0
> stat("/var/lib/lxc/bioreg-vmc01/config", {st_mode=S_IFREG|0644, st_size=1552, ...}) = 0
> futex(0x7fe5c5fce000, FUTEX_WAIT, 0, NULL
>
>
> This is the first container on the list.
>

Sorry for the massmail...

In outline there was a segfault.
I rebooted the machine, then there was no segfault, but api protocol error.
I downgraded lxc version, reboot and it was stuck.
I upgraded lxc (no reboot), and segfault is there.


I have two this kind of machines: lxc latest version from the daily ppa, zfs backend, but different 
kernel (3.2 vs. 3.8 - backported). 10-30 container. Both produce the issue.

There is a similar (actually a couple of days ago installed machine, with 3 easy containers and no 
issue).


I hope, it helps,

tamas




More information about the lxc-users mailing list