<div dir="ltr"><div><div><div><div><div><div><div>AAlso... just tried this, completely removed LXC and reinstalled it.<br><br></div>$ sudo apt-get purge lxc<br><br></div>$ sudo apt-get install lxc<br><br></div>then created a container<br>
<br></div>$ sudo lxc-create -t ubuntu -n my_cn1<br><br></div>$ sudo lxc-start -n my_cn1<br><br></div>after logging into the container I shut it down without doing anything else in the container<br><br></div>$ sudo shutdown -h now<br>
<br><div class="gmail_extra">Again, my host freezes, no mouse, no keyboard and its hard reset time again.<br><br></div><div class="gmail_extra">Just for reference again my host PC is:<br><br></div><div class="gmail_extra">
ubuntu 13.04 desktop version recently installed on this new system<br></div><div class="gmail_extra">16GB ram<br></div><div class="gmail_extra">3 - 2TB sata<br></div><div class="gmail_extra">BTRFS file system<br><br></div>
<div class="gmail_extra">So the Ubuntu install is only 2 weeks old and I've purged & reinstalled LXC and the problem still happens.<br></div><div class="gmail_extra">any debug tips would be good since the machine freezes up its hard to check at the time of the problem<br>
<br></div><div class="gmail_extra">brian<br><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 14, 2013 at 8:27 AM, brian mullan <span dir="ltr"><<a href="mailto:bmullan.mail@gmail.com" target="_blank">bmullan.mail@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>This morning I tried to shutdown a container from the host instead of from inside the container:<br>
<br></div> $ sudo lxc-shutdown -n my_cn<br><br></div>and same thing happens the host becomes frozen with no mouse, keyboard etc and a hard reset is only recourse<br>
<br><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 13, 2013 at 6:52 PM, brian mullan <span dir="ltr"><<a href="mailto:bmullan.mail@gmail.com" target="_blank">bmullan.mail@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">resending...<br><br><div class="gmail_quote">Ok... did the following:<br><div dir="ltr"><div><div>
<div><div><br></div>$ sudo su<br></div>$ shutdown -h now<br><br></div>Same problem... Host PC freezes/crashes, no mouse, keyboard, only Hard Boot</div><div><div>
<div><br><br></div>NOTE: I didn't capture this before but here is the sequence I see during shutdown just before the Host PC freezes/crashes.<br>
<br><div><img src="https://mail.google.com/mail/u/0/images/cleardot.gif" alt=""></div><div style="margin-left:40px"><i>The system is going down for halt NOW!<br>ubuntu@test:~$ <4>init: tty4 main process (256) killed by TERM signal<br>
<4>init: tty2 main process (260) killed by TERM signal<br><4>init: tty3 main process (262) killed by TERM signal<br>
<4>init: cron main process (266) killed by TERM signal<br><4>init: console main process (283) killed by TERM signal<br><4>init: tty1 main process (288) killed by TERM signal<br><4>init: hwclock-save main process (344) terminated with status 70<br>
TERM environment variable not set.<br><4>init: plymouth-upstart-bridge main process (348) terminated with status 1<br> * Asking all remaining processes to terminate...<br> ...done.<br> * All processes ended within 1 seconds....<br>
...done.<br>initctl: Event failed<br> * Deactivating swap...<br> ...fail!<br>umount: /run/lock: not mounted<br>umount: /run/shm: not mounted<br>mount: cannot mount block device /dev/mapper/ubuntu--vg-root read-only<br>
* Will now halt<br></i></div><div><div><div><div><div><div><div><br>Also doing some google searches I don't think I am the only one seeing this problem of the Host PC freezing/crashing after you issue a Shutdown command in the container.<br>
<div class="gmail_quote"><br>See these for some others seeming to have similar or same problem I am:<br><br></div><div style="margin-left:40px" class="gmail_quote"><div><a href="http://superuser.com/questions/630609/lxc-container-shutdown-on-ubuntu-make-the-system-stop-to-work/631429#631429" target="_blank">http://superuser.com/questions/630609/lxc-container-shutdown-on-ubuntu-make-the-system-stop-to-work/631429#631429</a><br>
<br>
</div>
</div><div style="margin-left:40px"><a href="http://permalink.gmane.org/gmane.linux.kernel.containers.lxc.general/5445" target="_blank">http://permalink.gmane.org/gmane.linux.kernel.containers.lxc.general/5445</a><br></div>
<br></div><div>Brian<br><br></div><div><br>---------- Forwarded message ----------<br>From: Michael Fox <<a href="mailto:michaelf@heimic.net" target="_blank">michaelf@heimic.net</a>><br>To: brian mullan <<a href="mailto:bmullan.mail@gmail.com" target="_blank">bmullan.mail@gmail.com</a>><br>
Cc: "<a href="mailto:lxc-users@lists.sourceforge.net" target="_blank">lxc-users@lists.sourceforge.net</a>" <<a href="mailto:lxc-users@lists.sourceforge.net" target="_blank">lxc-users@lists.sourceforge.net</a>><br>
Date: Wed, 14 Aug 2013 06:20:17 +1000<br>
Subject: Re: [Lxc-users] Running sudo shutdown -h now in container causes host to freeze/crash<br><div dir="ltr"><br>As
root what happens if you shutdown -h now in the container... let's take
out the use of sudo completely when running that command and sudo upto
root user and run it. Do you still get a crash/hang?<br><br>
Thanks</div><br><br>On Wed, Aug 14, 2013 at 2:06 AM, brian mullan <span dir="ltr"><<a href="mailto:bmullan.mail@gmail.com" target="_blank">bmullan.mail@gmail.com</a>></span> wrote:<br>
I've been having this problem for a while now. To get away from it I actually did a sudo apt-get purge lxc<div>
then reinstalled LXC but now the same problem is back again.</div><div><br></div><div>System: ubuntu 13.04 desktop</div>
<div><br></div><div>I create a container:</div><div><b>sudo lxc-create -t ubuntu -n my_cn</b><br></div><div><br></div><div>start it</div><div><b>sudo lxc-start -n my_cn</b></div><div><br></div><div><b>login</b></div><div>
add a desktop environment</div><div><b>sudo apt-get install lxde</b></div><div><br></div><div>I also add a remote desktop config to the container so I can access the desktop from the host</div><div>(I use x2go but I've also used vnc and others).</div>
<div><br></div><div>remote desktop from host always works!</div><div><br></div><div>but when I am done I exit the remote desktop session which kills that session in the container </div><div><br></div><div>I get back into the terminal session with the container and tell it to shutdown:</div>
<div><br></div><div><b>sudo shutdown -h now</b></div><div><br></div><div>everything looks normal as the container shutsdown except it never returns to the Host command prompt in the terminal<br></div><div><br></div><div>
At that point if I try to click on anything on the host (like start a 2nd terminal or start a browser)... </div>
<div><br></div><div>That 1st app on the host starts but then the entire Host freezes solid. </div><div><br></div><div>No mouse, no keyboard, no activity and the only thing left to do is a hard reset.</div><div><br></div>
<div>Any ideas of how I can troubleshoot this? or what might be happening? I've been using LXC for a long time</div><div>and I've not had this happen before.</div><div><br></div><div>thanks</div><span><font color="#888888"><span><font color="#888888"><div>
brian</div></font></span></font></span></div></div></div></div></div></div></div></div></div></div>
</div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>