From: Mike Fischer (mike.fischer_at_ipsi.fraunhofer.de)
Date: Mon 15 Sep 2003 - 15:47:38 BST
Hello fellow vserver-enthusiasts!
I've got a setup with a vserver acting as company webserver. The web
contents come from the NAS via NFS.
I know I cant do any mounting inside the server without the
CAP_SYS_ADMIN, which I dont want to use, as it encompasses too much.
(also I got confused that the hostname didnt get set)
So I worked my way around this by mounting the www-content dierectory on
the host-server (via the /etc/vservers/web01.sh script)
This worked up until today, when I changed the vserver's IPROOT to just
include the IP-addresses of virtual devices (i.e. the IP-addresses
assigned to eth0:1 eth0:2 and so on). When I had the vserver running and
wanted to cd to the NFS-dir, the whole shell refused to work (no matter
if that was inside the vserver's context or outside). Only way to get
the shell working again was to stop the vserver, which did some nasty
kill -9
Then I put an adress of a hardware network interface back into IPROOT
and it worked fine again.
So that leaves me baffled with the two questions of why and how:
Why this behavior?
How can I use an NFS-mount inside a vserver?
I thank you in advance for any ideas on this.
Kind regards,
Mike Fischer
Appendix: (sorry, but I've gotta munge the addresses with x,y,z)
ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:02:B3:BD:79:6A
> inet addr:X.Y.Z.50 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:19193 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5282 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:1574283 (1.5 Mb) TX bytes:729262 (712.1 Kb)
> Interrupt:24 Base address:0xece0 Memory:feae0000-feb00000
>
> eth0:1 Link encap:Ethernet HWaddr 00:02:B3:BD:79:6A
> inet addr:X.Y.Z.51 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:24 Base address:0xece0 Memory:feae0000-feb00000
>
> eth0:2 Link encap:Ethernet HWaddr 00:02:B3:BD:79:6A
> inet addr:X.Y.Z.41 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:24 Base address:0xece0 Memory:feae0000-feb00000
>
> eth0:3 Link encap:Ethernet HWaddr 00:02:B3:BD:79:6A
> inet addr:X.Y.Z.53 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:24 Base address:0xece0 Memory:feae0000-feb00000
>
> eth0:4 Link encap:Ethernet HWaddr 00:02:B3:BD:79:6A
> inet addr:X.Y.Z.56 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:24 Base address:0xece0 Memory:feae0000-feb00000
>
> eth1 Link encap:Ethernet HWaddr 00:06:5B:8F:98:AB
> inet addr:X.Y.Z.49 Bcast:X.Y.Z+1.255 Mask:255.255.254.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:28 Base address:0xdce0 Memory:fe8e0000-fe900000
A working IPROOT-Line:
> IPROOT="X.Y.Z.49 X.Y.Z.41 X.Y.Z.56 X.Y.Z.51"
An IPROOT-Line that doesn't work:
> IPROOT="X.Y.Z.41 X.Y.Z.56 X.Y.Z.51"