> Precisely which version of lxc were you using?
I just put back version 0.9.0-0ubuntu2 (as opposed to the 0.9.0 I built
from source) while on kernel 3.7.9-030709-generic and haven't yet run
into this issue (I assume that's the patch you mentioned). However, when
I update to kernel 3.8.6-030806-generic (leaving the same version of
lxc), 12 out of 100 containers experienced what looks like this exact
problem:
lxc-start 1365805078.586 NOTICE lxc_start - '/usr/local/bin/node'
started with pid '4107'
lxc-start 1365805078.586 INFO lxc_console - no console will be used
lxc-start 1365805078.586 WARN lxc_start - invalid pid for SIGCHLD
lxc-start 1365805115.998 INFO lxc_start - forwarded signal 2 to pid
4107
--
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/1168526
Title:
race condition causing lxc to not detect container init process exit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1168526/+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
