Thanks for all your help. Turned out to be some busybox issues.
Everything works now.
Matt
-Original Message-
From: Herbert Poetzl [mailto:[EMAIL PROTECTED]
Sent: Monday, September 18, 2006 9:06 PM
To: Matt Anger (manger)
Cc: vserver@list.linux-vserver.org
Subject: Re: [Vserver] VServer startup error
On Mon, Sep 18, 2006 at 02:58:58PM -0700, Matt Anger (manger) wrote:
When trying to start a VServer I receive the following error:
bash-2.05b# vserver test start
Usage: lsmod
lockfile: open(syncpipe): No such file or directory
Usage: lsmod
seems like lsmod has a different usage than the tools expect here, try
with --debug to see what actually is executed
lockfile: open(syncpipe): No such file or directory
looks like locking is slightly different than usual too ...
save_ctxinfo: execv(): No such file or directory
this might actually mean that executing an init or rc script inside the
guest failed
An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(/etc/rc.d/rc 3) failed.
Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm'
build
method knows how to deal with this, but on existing installations,
appending 'true' to this file will help.
Failed to start vserver 'test'
I am running Linux 2.6.17.11-vs2.1.1-rc31 with util-vserver-0.30.210
trying to start a vserver image I downloaded off the internet(which I
verified works on the build box running same kernel and util).
The box running vserver is an embedded system with limited
memory+storage hence I had to compile the kernel and util on a
memory+seperate
machine and then manually install the files necessary onto the
machine, so it is very possible I might I missed a necessary file.
Does anyone have any suggestions?
I'm pretty sure you have what you actually need, but some commands are
probably slightly different than on a 'normal' system (e.g. coming from
busybox or similar) ...
double check what is executed and fails with --debug as mentioned above,
then try to fix it up with your commands ...
HTH,
Herbert
Matt Anger
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver