[Bug 1177583] Re: lxc-list crash after lxc-destroy of a running container
[Expired for lxc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lxc (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177583] Re: lxc-list crash after lxc-destroy of a running container
To be clear - the per-container 'command' handler, which is a part of the lxc-start process, cannot multiplex, so if one command were to be, say, suspended while having an open connection to the handler, or if lxc-start itself were to be hung, that could cause lxc-info to hang (as it was doing for you), and lxc-destroy would hang while calling lxc-info (which it does to figure out if it is running). The key is to figure out how you got to that state. ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177583] Re: lxc-list crash after lxc-destroy of a running container
Could you please try sudo apt-get install python3-dbg lxc-dbg apport-retrace sudo apport-retrace -g _usr_bin_lxc-ls.0.crash (type 'where', show the output) Or, if that doesn't seem to work, mkdir yyy apport-unpack _usr_bin_lxc-ls.0.crash yyy cd yyy gdb python3 CoreDump where -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1177583] Re: lxc-list crash after lxc-destroy of a running container
So I followed your suggestions for retracing he apport dump and got these results (not much I'm afraid): http://paste.ubuntu.com/5645895/ (1st option); http://paste.ubuntu.com/5645890/ (2nd option). I'll try replicating the same steps I did before from scratch to see if I can reproduce it later today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
