Dan, > Have you tried turning off root squashing?
I already have no_squash_root set. Regards Darryl > Dan > > On Fri, 2003-07-25 at 00:48, Darryl Ross wrote: > > Hey All, > > > > Have been lurking for a while, but this is a first post. > > > > I'm building a new data centre for my employer, and having used vserver > > on my own hardware we decided to use it as a solution in the new data > > centre. > > > > The basic setup is I have two machines which are acting as file servers > > (600Gb each) which are mirrored using drbd and do fail-over using > > heartbeat. They export a file system using NFS. On top of that I have 4 > > machines which are the vserver application servers. > > > > What I would like to be able to do is run /vservers and /etc/vservers > > from NFS. This would make it easy to 'move' a virtual server from one > > application server to another with only the downtime required for a > > 'vserver vs stop' and then 'vserver vs start'. This would make it easier > > to cope with hardware failures on the application servers and also means > > that I can quite easily load balance the virtual servers across the > > hardware. > > > > Now, my problem is that when I try to start a vserver which is stored on > > NFS I get the following results: > > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > [EMAIL PROTECTED] root]# cat /etc/vservers/radius2.conf > > IPROOT="202.6.141.2" > > IPROOTDEV=eth0 > > ONBOOT=no > > S_HOSTNAME=radius2.e-access.com.au > > S_DOMAINNAME= > > S_NICE=5 > > S_FLAGS="lock nproc sched" > > ULIMIT="-H -u 1000" > > S_CAPS="CAP_NET_ADMIN CAP_SYS_CHROOT CAP_NET_BIND_SERVICE" > > > > [EMAIL PROTECTED] root]# mount > > /dev/md1 on / type ext3 (rw) > > none on /proc type proc (rw) > > /dev/md0 on /boot type ext3 (rw) > > none on /dev/pts type devpts (rw,gid=5,mode=620) > > none on /dev/shm type tmpfs (rw) > > 172.30.0.100:/mnt/data/vservers/conf on /etc/vservers type nfs > > (rw,addr=172.30.0.100) > > 172.30.0.100:/mnt/data/vservers/actual on /vservers type nfs > > (rw,addr=172.30.0.100) > > > > [EMAIL PROTECTED] root]# vserver radius2 start > > Starting the virtual server radius2 > > Server radius2 is not running > > ipv4root is now 202.6.141.2 > > Host name is now radius2.e-access.com.au > > New security context is 11 > > Can't chroot to directory . (Permission denied) > > > > [EMAIL PROTECTED] root]# mount > > /dev/md1 on / type ext3 (rw) > > none on /proc type proc (rw) > > /dev/md0 on /boot type ext3 (rw) > > none on /dev/pts type devpts (rw,gid=5,mode=620) > > none on /dev/shm type tmpfs (rw) > > 172.30.0.100:/mnt/data/vservers/conf on /etc/vservers type nfs > > (rw,addr=172.30.0.100) > > 172.30.0.100:/mnt/data/vservers/actual on /vservers type nfs > > (rw,addr=172.30.0.100) > > none on /vservers/radius2/proc type proc (rw) > > none on /vservers/radius2/dev/pts type devpts (rw) > > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > I have done a google for this error, and the only references I can turn > > up are to do with the permissions on /vservers. The permission denied > > error occurs whether or not /vservers is mode 000 or mode 755 > > (root:root). Additionally, /proc and /dev/pts within the virtual server > > are mounted afterwards and the IP alias is also active. > > > > The application servers are running: > > - Redhat 9.0 (with updates) > > - vserver 0.22 (I also tried 0.23 with no difference) > > - kernel 2.4.21ctx-17 (from the website) > > > > What I would like is if there is some way I can store /vservers on my > > file servers and remote mount them. have tried NFS, I don't think Samba > > will work and I looked at Coda, but that also had problems (you have to > > authenticate to get a kerberos token each session). > > > > > > Does anyone know how I can get NFS working, or if there is some other > > way to remote mount /vservers and get it to work? > > > > TIA > > Darryl >
