Here is the infomation: But note that with the previous kernel patch it all works ok. So with 2.4.20ctx-16 it doesn't work, and with 2.4.19ctx-14 ok.
exports file on the nfs server /nfs/vservers 210.54.14.0/255.255.255.0(rw,no_root_squash,sync) /nfs/vservers-conf 210.54.14.0/255.255.255.0(rw,no_root_squash,sync) server1:~# ls -ld /vservers* d--------- 34 root root 4096 Dec 20 09:52 /vservers d--------- 34 root root 4096 Dec 20 09:52 /vservers-nfs d--------- 3 root root 4096 Jan 10 13:45 /vservers2 server1:~# ls -ld /vservers*/test drwxr-xr-x 20 root root 4096 Dec 20 10:12 /vservers-nfs/test drwxr-xr-x 20 root root 4096 Dec 20 10:12 /vservers/test drwxr-xr-x 20 root root 4096 Dec 20 10:12 /vservers2/test server1:~# server1:~# umount /vservers-nfs/ server1:~# ls -ld /vservers*/test drwxr-xr-x 20 root root 4096 Dec 20 10:12 /vservers2/test server1:~# ls -ld /vservers* drwxr-xr-x 2 root root 4096 Apr 12 2002 /vservers drwxr-xr-x 2 root root 4096 Jan 10 13:59 /vservers-nfs d--------- 3 root root 4096 Jan 10 13:45 /vservers2 server1:~# mount /vservers-nfs server1:~# mount --bind /vservers-nfs/ /vservers server1:~# vserver test start Starting the virtual server test Server test is not running broadcast: Unknown host ipv4root is now 210.54.14.116 Host name is now test New security context is 11 Can't chroot to directory . (Invalid argument) server1:~# umount /vservers umount: /vservers: device is busy server1:~# vserver test stop Stopping the virtual server test Server test is not running server1:~# umount /vservers server1:~# mount --bind /vservers2/ /vservers server1:~# vserver test start Starting the virtual server test Server test is not running broadcast: Unknown host ipv4root is now 210.54.14.116 Host name is now test New security context is 12 Starting system logging: syslog-ngError opening file /proc/kmsg for reading (Operation not permitted) Error initializing configuration, exiting. . Starting internet superserver: inetd. Starting network management services: snmpd snmptrapd. Starting OpenBSD Secure Shell server: sshd. Starting periodic command scheduler: cron. Starting web server: apache[Mon Jan 13 15:01:17 2003] [alert] apache: Could not determine the server's fully qualified domain name, using 210.54.14.116 for ServerName . server1:~# vserver test stop Stopping the virtual server test Server test is running broadcast: Unknown host ipv4root is now 210.54.14.116 New security context is 12 Stopping periodic command scheduler: cron. Stopping web server: apacheNo /usr/sbin/apache found running; none killed. . Stopping internet superserver: inetd. Stopping network management services: snmpd snmptrapd. Stopping OpenBSD Secure Shell server: sshd. Saving the System Clock time to the Hardware Clock... hwclock is unable to get I/O port access: the iopl(3) call failed. Hardware Clock updated to Mon Jan 13 15:01:26 NZDT 2003. Stopping system logging: syslog-ngstart-stop-daemon: warning: failed to kill 21895: No such process . Sending all processes the TERM signal... done. Sending all processes the KILL signal... done. Saving random seed... done. Unmounting remote filesystems... done. NOT deconfiguring network interfaces: network shares still mounted. Deactivating swap... done. Unmounting local filesystems... umount2: Invalid argument umount: /dev/hdv1: not found umount: /: Illegal seek done. mount: permission denied Rebooting... sleeping 5 seconds Killing all processes and the strace has just confused me.. Thou I can mail it, if someone wants to browse... :) Fran. On Mon, 2003-01-13 at 11:08, Sam Vilain wrote: > Are you setting no_root_squash on the NFS server? > > If that doesn't help, give us: > - your /etc/exports line on the NFS server > - output from `ls -ld /vservers* /vservers*/test' on both > servers, before and after any NFS mount operation (ie, what are the > permissions of the directories under the mounts, sometimes relevant). > - the exact commands you are running (cut and paste the shell session). > > Prepending `strace -fae' should show you the actual system call that is > receiving EPERM, which might shed some light on the issue. > > Good luck, > Sam. > > On Mon, 13 Jan 2003 09:39, you wrote: > > Didn't help with me... > > > > I have > > > > on the local disk I have /vservers2 > > on an nfs array I have /vservers-nfs > > > > In side of the /vservers2 I have 1 folder called test ( the vserver). > > > > In side of the /vservers-nfs the same. > > > > They have the same permissions. > > > > I then do a mount --bind /vservers2 /vservers > > > > vserver test start > > > > OK > > > > vserver test stop > > > > umount /vservers > > mount --bind /vservers-nfs /vservers > > > > vserver test start > > > > Fails with > > Starting the virtual server test > > Server test is not running > > ipv4root is now 210.54.14.116 > > Host name is now test > > New security context is 10 > > Can't chroot to directory . (Permission denied) > > > > Thoughts??? > > > > > > Fran. > > > > On Mon, 2003-01-13 at 09:17, Dinesh Mistry wrote: > > > AHhh nope I am not but I was running a local loop back file system. I > > > figured out the problem though. > > > > > > They ask you to chmod 000 /vservers/VSERVERNAME > > > > > > This breaks the vserver if you just chmod 000 /vservers then it works. > > > > > > > > > > > > -------------------------------------------- > > > Dinesh Mistry > > > > > > YourHostDirect > > > 1-800-210-6757 > > > > > > Better, Faster and more Reliable Hosting > > > http://www.yourhostdirect.com > > > -------------------------------------------- > > > > > > > > > -----Original Message----- > > > From: Fran Firman [mailto:[EMAIL PROTECTED]] > > > Sent: Sunday, January 12, 2003 3:13 PM > > > To: Dinesh Mistry > > > Subject: Re: Did you fix this? > > > > > > Are you also using a NFS array to store the vserver data/folder? > > > > > > If I run the vserver on the local HD it works ok. > > > > > > F. > > > > > > On Sun, 2003-01-12 at 10:49, Dinesh Mistry wrote: > > > > Just upgraded to 2.4.19ctx-15 and vserver 0.22 > > > > > > > > > > > > > > > > > > > > > > > > I now get the error. > > > > > > > > > > > > > > > > server4:~# vserver knottsberry start > > > > > > > > Starting the virtual server knottsberry > > > > > > > > Server knottsberry is not running > > > > > > > > ipv4root is now 210.54.14.137 > > > > > > > > Host name is now knottsberry > > > > > > > > New security context is 15 > > > > > > > > Can't chroot to directory . (Permission denied) > > > > > > > > > > > > > > > > > > > > > > > > This is on a debian host. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I am having the same problem L > > > > > > > > > > > > > > > > -------------------------------------------- > > > > > > > > Dinesh Mistry > > > > > > > > > > > > > > > > YourHostDirect > > > > > > > > 1-800-210-6757 > > > > > > > > > > > > > > > > Better, Faster and more Reliable Hosting > > > > > > > > http://www.yourhostdirect.com > > > > > > > > -------------------------------------------- -- Fran Firman <[EMAIL PROTECTED]>
