From: Etienne Schellerup (etienne_at_synclude.com)
Date: Thu 05 Sep 2002 - 07:47:24 BST
I had a similar problem after unifying two vservers not located on the
same partition. What happened was that most files in /bin /sbin /usr/bin
and others got simply deleted (hence the vserver doesn't boot). Try
deunifying the two if that is what you did:
/usr/lib/vserver/vunify --undo basevserver target -- ALL
Or alternatively copy all the files back by hand...
Hope this helps,
On Wed, 2002-09-04 at 20:39, John Lyons wrote:
> I've just set up a new host server RedHat7.2 running 2.4.19ctx-13 and
> vserver-admin-0.19-1 vserver-0.19-1
> Kernel patch seems fine, and the host server is ok.
> Trying to start any virtual servers is giving.
> [root_at_svr11 vservers]# vserver vs189 start
> Starting the virtual server vs189
> Server vs189 is not running
> ipv4root is now xxx.xxx.xx.189
> Host name is now vs189.xxxx.xxx
> Domain name is now xxxx.xxx
> New security context is 189
> Can't execute /etc/rc.d/rc (No such file or directory)
> (I've removed xxx.xxx etc for my own security)
> The virtual server ran quite happily on an older host server 2.4.18ctx-10.
> Conf file is
> S_FLAGS="lock sched nproc"
> ULIMIT="-H -u 200"
> Can anyone spot the problem?
> John Lyons
> Netserve Consultants Ltd
-- Etienne Schellerup Director & Technical Consultant Synclude Ltd.
BE Phone: +32 (0) 485 899 686 - Fax: +32 (0) 2 610 7707 http://www.synclude.com