Subject: Re: [vserver] gentoo baselayout-2 conversion problem
From: Chuck <chuck@sbbsnet.net>
Date: Tue, 26 Aug 2008 07:35:10 -0400

On Tuesday 26 August 2008, Ed W wrote:
> 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
> >   
> 
> I did not have this problem a month of so ago with open-rc 0.2.3 and 
> some older udev and I *do* have it now that I have updated all my 
> vservers to openrc 0.2.5.  I had assumed that openrc updates were 
> responsible, but not tracked that down
> 
> Try reverting openrc to 0.2.3 and see if this fixes things and if so 
> perhaps a diff to see what caused it?
> 
will try. might be a bit though.. beginning today we are moving a bunch of new 
servers into the noc to replace and support older ones so my schedule is 
going to be beyond full for the next week or two.


> Ed W
> 



-- 

Chuck