touch-packages team mailing list archive

[Nikola Krzalic <nikola@xxxxxxxxxxx>]

Looks like the lxc-start command got stuck, after killing the process
everything went back to normal.

root@ares:~# netstat -x | grep lxc
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command
unix  2      [ ]         STREAM     CONNECTING    0
 @/var/lib/lxc/myvm/command

root@ares:~# ps -ef | grep lxc
root      1697  1250  0 Okt06 ?        00:00:00 strace lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root      1704  1697  0 Okt06 ?        00:00:00 lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
lxc-dns+ 13856     1  0 Okt05 ?        00:00:00 dnsmasq -u lxc-dnsmasq
--strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid
--conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254
--dhcp-lease-max=253 --dhcp-no-override --except-interface=lo
--interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases
--dhcp-authoritative

root@ares:~# ps -ef | grep 1697
root      1697  1250  0 Okt06 ?        00:00:00 strace lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root      1704  1697  0 Okt06 ?        00:00:00 lxc-start -n myvm -f
myvm.conf --logfile=vm.log --logpriority=NOTICE
root     15861 21116  0 08:12 pts/16   00:00:00 grep --color=auto 1697

root@ares:~# kill -3 1697
root@ares:~# ps -ef | grep lxc-start
root     15870 21116  0 08:13 pts/16   00:00:00 grep --color=auto lxc-start

root@ares:~# lxc-ls --fancy
NAME  STATE  IPV4  IPV6  AUTOSTART
----------------------------------

root@ares:~# lxc-destroy -n myvm
Container is not defined


still, I find it a bit strange that not even lxc-ls was working properly....

On Mon, Oct 6, 2014 at 4:57 PM, Serge Hallyn <1377973@xxxxxxxxxxxxxxxxxx>
wrote:

> thanks for reporting this bug.
>
> Could you please show:
>
> 1. The result of 'netstat -x | grep lxc'
>
> 2. ps -ef | grep lxc
>
>  status: incomplete
>
>
> ** Changed in: lxc (Ubuntu)
>        Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1377973
>
> Title:
>   lxc-destroy/lxc-stop gets stuck
>
> Status in “lxc” package in Ubuntu:
>   Incomplete
>
> 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
>


-- 
Pozdrav / Regards,

Nikola Krzalic.

-- 
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:
  Incomplete

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