Quoting Nikola Krzalic (nik...@krzalic.com):
> Looks like the lxc-start command got stuck, after killing the process
> everything went back to normal.
...
> still, I find it a bit strange that not even lxc-ls was working properly....
Right, we should find a way to keep lxc-stop and lxc-ls from hanging in
this case. Perhaps after a (reasonably long) timeout we should assume
it is dead, hard-kill the container (in this case the owner of the
command socket), and continue.
(marking medium importance rather than high, per guidelines, since it
can be detected and worked around)
status: confirmed
importance: medium
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
** Changed in: lxc (Ubuntu)
Status: Incomplete => Confirmed
--
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/1377973
Title:
lxc-destroy/lxc-stop gets stuck
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+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
