touch-packages team mailing list archive

[Serge Hallyn <1261338@xxxxxxxxxxxxxxxxxx>]

Thanks for the information.  Indeed, lxc-stop -k still works by talking
to the lxc monitor.  What appears to have happened here is that the
monitor itself is frozen.

Could you please show full output of:

ps -ef

Then do 'ps -ef | grep lxc-start' to find the lxc-start process for the
hung container.  In one terminal do

sudo strace -f -odebug.out -p $pid

where $pid is the process id of the lxc-start.  Then in another terminal
again do

lxc-stop -n $container -k

and attach the file debug.out to this report.

** Changed in: lxc (Ubuntu)
       Status: Invalid => Incomplete

-- 
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/1261338

Title:
  lxc-stop and even lxc-stop -k can hang

Status in “lxc” package in Ubuntu:
  Incomplete

Bug description:
  and even 'lxc-stop -k -t <timeout>' can hang :-/

  The context is an automated test run with otto using a lxc-container
  trigerring a kernel crash on the host.

  The host is still alive and so is the container but trying to
  implement a catch-all to stop a container left running is blocked
  because there is no way in this particular case to stop the container.

  The only alternative so far is to reboot the host :-/

  http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-
  daily_release/label=qa-intel-4000/951/console is one occurrence where
  the kernel crashed and 'lxc-stop -k -t 120 -n
  trusty-i386-20131216-0008' hanged requiring the job to be aborted.

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