From: Justin M Kuntz (jkuntz_at_prominic.com)
Date: Fri 10 May 2002 - 22:30:46 BST
Joel --
Thank you for your advice below. You are right, vservers do create the
ipalias when they are started. I've followed the two steps you suggested
below and now here is what happens:
Do you have any idea what I need to do next to get it working? I mean the
message "Server 0001 is not running" is showing up both after the start
command and after the enter command, so I'm assuming something is still
wrong.
Thanks!
Justin
[root_at_linux-4 opt]# /usr/sbin/vserver 0001 start
Starting the virtual server 0001
Server 0001 is not running
ipv4root is now 172.16.128.100
Host name is now jmk1.prominic.com
Domain name is now prominic.com
New security context is 16
[root_at_linux-4 opt]# /usr/sbin/vserver 0001 enter
Server 0001 is not running
ipv4root is now 172.16.128.100
Host name is now jmk1.prominic.com
Domain name is now prominic.com
New security context is 17
[root_at_jmk1 /]#
"Joel Vandal"
<jvandal_at_monse To: <vserver_at_solucorp.qc.ca>
rveur.net> cc:
Fax to:
05/10/2002 Subject: Re: [vserver] SIOCS... errors - any ideas?
02:18 PM
Please respond
to vserver
> Starting the virtual server 0001
> Server 0001 is not running
> SIOCSIFADDR: File exists
> SIOCSIFFLAGS: Cannot assign requested address
> SIOCSIFNETMASK: Cannot assign requested address
> SIOCSIFBRDADDR: Cannot assign requested address
> SIOCSIFFLAGS: Cannot assign requested address
If I'm not wrong, vservers will automatically create the interface.
To remove it, try: " ifconfig eth0:0 down " and restart vservers.
> Can't chroot to directory . (Permission denied)
I've solve this problem using:
chmod 000 /vservers
chmod 644 /vservers/0001
-- Joel Vandal