| 
		
			| "reboot" inside a container stops the container [message #42405] | Wed, 13 April 2011 09:16  |  
			| 
				
				
					|  Benjamin Henrion Messages: 51
 Registered: February 2011
 | Member |  |  |  
	| Hi, 
 I found out that typing "reboot" in a container halts the whole
 container, making it unreacheable (the container itself is not running
 anymore, checking with vzlist on the physical machine).
 
 Any idea if there is another command that kills all the processes and
 restart the container from within a root shell on the container (yes I
 know that you can do that with 'vzctl restart CTID' on the HN)?
 
 Best,
 
 --
 Benjamin Henrion <bhenrion at ffii.org>
 FFII Brussels - +32-484-566109 - +32-2-4148403
 "In July 2005, after several failed attempts to legalise software
 patents in Europe, the patent establishment changed its strategy.
 Instead of explicitly seeking to sanction the patentability of
 software, they are now seeking to create a central European patent
 court, which would establish and enforce patentability rules in their
 favor, without any possibility of correction by competing courts or
 democratically elected legislators."
 |  
	|  |  | 
	|  | 
	| 
		
			| Re:  "reboot" inside a container stops the container [message #42412 is a reply to message #42405] | Wed, 13 April 2011 16:37  |  
			|  |  
	| On 13 April 2011 13:16, Benjamin Henrion <bh@udev.org> wrote: > Hi,
 >
 > I found out that typing "reboot" in a container halts the whole
 > container, making it unreacheable (the container itself is not running
 > anymore, checking with vzlist on the physical machine).
 
 Which vzctl and kernel do you use?
 
 In case of vzctl < 3.0.25 reboot is performed by the vpsreboot cron
 script which is
 called from cron every 5 minutes by default. Check if your cron daemon
 is running,
 check that you have that job installed, and note that since this job
 is run every 5
 minutes, your container can be done for as long as 5 minutes.
 
 In case of vzctl >= 3.0.25 (and a decent/recent kernel) reboot is performed by a
 daemon called vzeventd. Check that vzevent kernel module is loaded,
 that vzeventd
 daemon is running and included in autostart.
 
 Kir Kolyshkin
 
   |  
	|  |  |