Hi all, Environment : Debian Lenny 5.03 amd64, netinst installation (no Desktop, anything else but the basic install) Supplementary packages : apt-get install linux-image-2.6.26-2-vserver-amd64 util-vserver vserver-debiantools ssh /etc/apt/sources.list : deb http://debian.univ-reims.fr/debian/ lenny main /etc/apt/apt.conf : Acquire::http::Proxy "http:// <user>:<password>@<proxy>:<port>/" *(Note that the install works fine with this apt configuration)* Problem : cannot create guest, it seems to be indefinitely halted at "retrieving release" # vserver machina build -m debootstrap --context 117 --hostname machina --interface eth4:172.16.63.117/25 -- -d lenny I: Retrieving Release *...Waiting for a while (~ 1 hour)*...* Then hitting Ctrl-C* ^CE: Interrupt caught ... exiting chroot-sh: open("/etc/apt/sources.list"): No such file or directory chroot-sh: open("/etc/apt/apt.conf"): No such file or directory >>> Executing post install script ... secure-mount: chdir("/tmp"): No such file or directory /etc/vservers/machina/fstab:2:1: failed to mount fstab-entry vcontext: execvp("bash"): No such file or directory wait(): No child processes An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (bash -c exec > /dev/null exec 2> /dev/null trap 'kill -s 9 -- -1; exit 0' INT sleep 30 kill -s 15 -- -1 sleep 1 kill -s 9 -- -1) 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 'machina' 'vserver ... suexec' is supported for running vservers only; aborting... *This message repeated 5 times...* Thanks in advance for the help, Yon
secure-mount: chdir("/tmp"): No such file or directory
/etc/vservers/machina/fstab:2:1: failed to mount fstab-entry
vcontext: execvp("bash"): No such file or directory
wait(): No child processes
An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(bash -c
exec > /dev/null
exec 2> /dev/null
trap 'kill -s 9 -- -1; exit 0' INT
sleep 30
kill -s 15 -- -1
sleep 1
kill -s 9 -- -1) 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.