touch-packages team mailing list archive

[Dan Poler <dan.poler@xxxxxxxxxxxxx>]

Quoting Serge Hallyn
> 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.

I'm seeing this behaviour happen in Vivid although in my case the
"stuck" container is perfectly responsive and is working fine e.g. if I
ssh into it. So the assumption that the container is dead and should be
killed may not be the answer... I'd rather have the container work and
lxc-ls broken than the other way around.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1377973

Title:
  lxc-destroy/lxc-stop gets stuck

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu 14.04 I ran lxc-start with a custom built container and
  interrupted the setup before it could finish. Now lxc-ls --fancy, lxc-
  destroy -n container or lxc-stop -n container are getting stuck. LXC
  package version is 1.0.5-0ubuntu0.1

  Output from strace:

  # strace lxc-destroy -n myvm
  <....>
  mkdir("/", 0755)                        = -1 EEXIST (File exists)
  mkdir("/run/", 0755)                    = -1 EEXIST (File exists)
  mkdir("/run/lock/", 0755)               = -1 EEXIST (File exists)
  mkdir("/run/lock/lxc//", 0755)          = -1 EEXIST (File exists)
  mkdir("/run/lock/lxc//var/", 0755)      = -1 EEXIST (File exists)
  mkdir("/run/lock/lxc//var/lib/", 0755)  = -1 EEXIST (File exists)
  mkdir("/run/lock/lxc//var/lib/lxc", 0755) = -1 EEXIST (File exists)
  stat("/var/lib/lxc/myvm/config", 0x7fff06d64f50) = -1 ENOENT (No such file or directory)
  stat("/var/lib/lxc/myvm/partial", 0x7fff06d64e80) = -1 ENOENT (No such file or directory)
  socket(PF_LOCAL, SOCK_STREAM, 0)        = 3
  connect(3, {sa_family=AF_LOCAL, sun_path=@"/var/lib/lxc/myvm/command"}, 28) = 0
  getuid()                                = 0
  getgid()                                = 0
  sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=2028, uid=0, gid=0}}, msg_flags=0}, MSG_NOSIGNAL) = 16
  recvmsg(3,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+subscriptions