reboot in a container gets somehow stuck

[Holger Hans Peter Freyther]

Binary package hint: lxc

This is on Ubuntu Natty with a Natty container (lxc-create -t natty). Forcing a reboot in the container will fail.

1.) the container will not reboot
2.) lxc-ls will list the container twic
3.) lxc-start will hang somewhere printing this on the console

sudo lxc-start -n qtwebkit
init: udev main process (23) terminated with status 1
init: udev main process ended, respawning
init: udevmonitor main process (28) terminated with status 2
init: udev-fallback-graphics main process (33) terminated with status 1
init: networking main process (39) terminated with status 1
init: plymouth main process (6) killed by ABRT signal
init: plymouth-splash main process (38) terminated with status 2

[Serge Hallyn (serge-hallyn)]

Are you still having this problem? If so, how did you create the container?

[Holger Hans Peter Freyther (holger+lp)]

I am back to using FreeBSD jails. The initial message of the bug report says I was using lxc-create -t natty.

[Serge Hallyn (serge-hallyn)]

Thanks. Marking invalid as the victim system is no longer available.

[exa (examachine)]

I see the same error while trying to boot from nfs. I saw it in syslog of the nfs client (after getting a sulogin console). Is this normal? I see that udev-fallback-graphics also failed, is this related? Why, is it a fatal error that graphics cannot be started? That does not make much sense to me. After this, the system tends to freeze, silently.

Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics main process (1295) terminated with status 1
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics goal changed from start to stop
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from running to stopping
Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from stopping to killed
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from killed to post-stop
Jun 1 10:46:11 cylon-fermi-unset init: udev-fallback-graphics state changed from post-stop to waiting
Jun 1 10:46:11 cylon-fermi-unset init: Handling startup/failed event
Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped/failed event
Jun 1 10:46:11 cylon-fermi-unset init: Handling stopped event
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash goal changed from stop to start
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from waiting to starting
Jun 1 10:46:11 cylon-fermi-unset init: Handling starting event
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from starting to pre-start
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from pre-start to spawned
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash main process (1303)
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from spawned to post-start
Jun 1 10:46:11 cylon-fermi-unset init: plymouth-splash state changed from post-start to running
Jun 1 10:46:11 cylon-fermi-unset init: Handling started event
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb goal changed from stop to start
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from waiting to starting
Jun 1 10:46:11 cylon-fermi-unset init: Handling starting event
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from starting to pre-start
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from pre-start to spawned
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb main process (1304)
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from spawned to post-start
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from post-start to running
Jun 1 10:46:11 cylon-fermi-unset init: Handling started event
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb main process (1304) exited normally
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb goal changed from start to stop
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from running to stopping
Jun 1 10:46:11 cylon-fermi-unset init: Handling stopping event
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from stopping to killed
Jun 1 10:46:11 cylon-fermi-unset init: setvtrgb state changed from ki...

[Serge Hallyn (serge-hallyn)]

@exa,

how did you create your container? Do you get the same error when you create a container on the local filesystem?