It never happened again (and may have been a misuse involving immortal
sudo subprocesses but I'm blurry on the details), marking invalid but
fixed released may be correct as well.
** Changed in: lxc (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are
[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/
Not seeing anything obviously wrong here...
To rule out a few more things, when you get the hanging "lxc-stop -n container
-k", can you do and paste the output of:
- ps faux
- dmesg
Thanks!
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: lxc (Ubuntu)
Impo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => 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/1261338
T
** Changed in: lxc (Ubuntu)
Status: Incomplete => New
--
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/1261338
Title:
lxc-stop and even lxc-stop -k can hang
To manage notification
The second option, if you do not use the -d
all post in file post
** Attachment added: "post"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+attachment/4179069/+files/post
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
debug file
** Attachment added: "ivan.zip"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+attachment/4179070/+files/ivan.zip
--
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/bug
debug file
** Attachment added: "debug.out"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+attachment/4179056/+files/debug.out
--
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/b
all post in file post
** Attachment added: "post"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+attachment/4179055/+files/post
--
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/
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 containe
This problem was repeated to me.
executed commands
sudo apt-get install lxc
sudo lxc-create -t ubuntu -n p1
sudo lxc-start -n p1
sudo lxc-stop -n p1 ==execution hangs
sudo strace -f lxc-stop -k -n p1==
execve("/usr/bin/lxc-stop", ["lxc-stop", "-k", "-n", "p1"], [/* 26 vars */]) = 0
brk(0)
ivan@ivan-Satellite-A40:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu
Hello! This problem also manifested itself in me. I performed the
following commands
sudo apt-get install lxc
sudo lxc-create -t ubuntu -n p1
sudo lxc-kill -n p1 lxc-kill: command not found
sudo lxc-stop -n p1 == execution hangs
sudo strace -f lxc-stop -k -n p1
execve("/usr/bin/lxc-stop",
Sorry for not providing timely feedback there (nor a reproducing env).
Truth is this hasn't recur so marking invalid seems fair.
Thanks for the help nevertheless, if it happens again, I'll make sure to
have such a reproducing env before re-opening this bug.
--
You received this bug notification
I vaguely remember discussing this on IRC.
IIRC the case was something in the container getting stuck in D state
because of a kernel bug. In such case, the container couldn't be killed
as anything attempting to do so would get stuck too.
Anyway, this is pretty unfortunate but it's a kernel bug an
(I should've explicitly asked: exactly what steps are you taking to
reproduce this)
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
What exactly is the kernel crash being triggered on the host?
What does 'sudo strace -f lxc-stop -k -n ' show?
What does the file outout show after running 'sudo lxc-stop -l info -o
outout -n ' ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
17 matches
Mail list logo
