Subject: Re: [vserver] gentoo baselayout-2 conversion problem
From: Chuck <chuck@sbbsnet.net>
Date: Sun, 24 Aug 2008 17:05:24 -0400

interesting update.... i switched to gentoo init style on this converted 
guest. i just went back to plain and i see no error and it has a quick stop 
with no abnormal delays. tested this 3 times and each time the gentoo init 
style errors... 

maybe older systems upgraded by world and then upgraded to baselayout-2 still 
require init style plain?


On Sunday 24 August 2008, Chuck wrote:
> i converted an older guest that was brought up to date with emerege world to 
> baselayout2 (our template model) and have a problem in shutdown. i get these 
> messages. things are fine until near the end.
> 
>  * Stopping local ...   [ ok ]
>  * Stopping vixie-cron ...   [ ok ]
>  * Saving random seed ...   [ ok ]
>  * Stopping chrooted named ...  [ ok ]
>  * Stopping syslog-ng ...   [ ok ]
> WARNING: could not determine runlevel - doing soft halt
>   (it's better to use shutdown instead of halt from the command line)
> shutdown: timeout opening/writing control channel /dev/initctl
> init: timeout opening/writing control channel /dev/initctl
> /usr/lib64/util-vserver/vserver.stop: line 96:  9034 
> 
Killed                  "${NICE_CMD[@]}" "${CHBIND_CMD[@]}" "$_VSPACE" --enter "$S_CONTEXT"
"${OPTS_VSPACE[@]}" -- "$_VTAG" --migrate "${OPTS_VTAG_ENTER[@]}" --silent -- 
> $_VCONTEXT 
> $SILENT_OPT --migrate --chroot --xid "$S_CONTEXT" -- "${INITCMD_STOP[@]}"
> 
> i think the upgrade emerged not only baselayout-2 and openrc but also 
init-0.  
> when i first tried to start it i found itwas missing a file
> 
> /lib/rc/sh/init-vserver.sh
> 
> so i copied that from the successful 2008.0 stage3->baselayout2 conversion 
> that i did previously. i also think that a uDv world was done after a 
> successful conversion of the older template because i do not remember any 
> problems starting or stopping it before that..
> 
> any clues what may have happened? this is on an x86_64 (amd64) guest. the 
> above init-vserver.sh file was taken from an i686 guest.
> 
> 
> 
> 
> 
> -- 
> 
> Chuck
> 



-- 

Chuck