Mark Weaver wrote:
Collins Richey wrote:
On 4/24/05, Mark Weaver mdw1982@mdw1982.com wrote:
Hi all,
I've got some insanity with mounting an NFS share that before reloading my workstation afresh worked perfectly, but now refuses to mount.
Actually there are two servers with shares mounted. (1) Mandrake 10.0 file server - two shares - mount perfectly (2) Fedora Core 3 - one share - can't mount to save my life!
My workstation is CentOS 4. I reloaded it to get rid of the FC3 installation at the front of the main drive and recover some space on the second drive moving CentOS to the main drive. Everything else works wonderfully as advertised. The following is the only feedback I'm getting when attempting to mount the share from the FC3 server. (the shares on the file server mount perfectly)
SERVER: Apr 24 09:43:41 mail rpc.mountd: authenticated mount request from 192.168.0.252:921 for /var/www (/var/www)
CLIENT: Mounting NFS filesystems: mount: 192.168.0.4:/var/www failed, reason given by server: Permission denied
What does your fstab entry for the share look like?
sorry about that... I knew I'd forget something.
the fstab entry on the client machine appears thusly: 192.168.0.4:/var/www /mnt/www nfs rsize=8192,wsize=8192,auto,hard 0 0
The exports file on the server appears as this: /var/www 192.168.0.252(rw)
(the IP of the client machine is 192.168.0.252)
Have you tried to mount another test share on the server with no options/IP restrictions?
Dean.
Plant, Dean wrote:
Mark Weaver wrote:
Collins Richey wrote:
On 4/24/05, Mark Weaver mdw1982@mdw1982.com wrote:
Hi all,
I've got some insanity with mounting an NFS share that before reloading my workstation afresh worked perfectly, but now refuses to mount.
Actually there are two servers with shares mounted. (1) Mandrake 10.0 file server - two shares - mount perfectly (2) Fedora Core 3 - one share - can't mount to save my life!
My workstation is CentOS 4. I reloaded it to get rid of the FC3 installation at the front of the main drive and recover some space on the second drive moving CentOS to the main drive. Everything else works wonderfully as advertised. The following is the only feedback I'm getting when attempting to mount the share from the FC3 server. (the shares on the file server mount perfectly)
SERVER: Apr 24 09:43:41 mail rpc.mountd: authenticated mount request from 192.168.0.252:921 for /var/www (/var/www)
CLIENT: Mounting NFS filesystems: mount: 192.168.0.4:/var/www failed, reason given by server: Permission denied
What does your fstab entry for the share look like?
sorry about that... I knew I'd forget something.
the fstab entry on the client machine appears thusly: 192.168.0.4:/var/www /mnt/www nfs rsize=8192,wsize=8192,auto,hard 0 0
The exports file on the server appears as this: /var/www 192.168.0.252(rw)
(the IP of the client machine is 192.168.0.252)
Have you tried to mount another test share on the server with no options/IP restrictions?
Dean.
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
On Mon, 2005-04-25 at 06:22 -0400, Mark Weaver wrote:
Plant, Dean wrote:
Mark Weaver wrote:
Collins Richey wrote:
On 4/24/05, Mark Weaver mdw1982@mdw1982.com wrote:
Hi all,
I've got some insanity with mounting an NFS share that before reloading my workstation afresh worked perfectly, but now refuses to mount.
Actually there are two servers with shares mounted. (1) Mandrake 10.0 file server - two shares - mount perfectly (2) Fedora Core 3 - one share - can't mount to save my life!
My workstation is CentOS 4. I reloaded it to get rid of the FC3 installation at the front of the main drive and recover some space on the second drive moving CentOS to the main drive. Everything else works wonderfully as advertised. The following is the only feedback I'm getting when attempting to mount the share from the FC3 server. (the shares on the file server mount perfectly)
SERVER: Apr 24 09:43:41 mail rpc.mountd: authenticated mount request from 192.168.0.252:921 for /var/www (/var/www)
CLIENT: Mounting NFS filesystems: mount: 192.168.0.4:/var/www failed, reason given by server: Permission denied
What does your fstab entry for the share look like?
sorry about that... I knew I'd forget something.
the fstab entry on the client machine appears thusly: 192.168.0.4:/var/www /mnt/www nfs rsize=8192,wsize=8192,auto,hard 0 0
The exports file on the server appears as this: /var/www 192.168.0.252(rw)
(the IP of the client machine is 192.168.0.252)
Have you tried to mount another test share on the server with no options/IP restrictions?
Dean.
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
I just had some fun with this yesterday using Centos 4 as the nfs server and an FC3 client.
Using hostnames it played nice, but with ip addresses I had permissions issues. I am not using fstab although from this post it down not appear to be client side issue.
tcpdump/ethereal can be most revealing in these cases as well as debugging.
My server is using SELINUXTYPE=targeted, not sure if that really matters, still getting my feet wet with selinux.
Ted
On 04/25/2005 03:22 AM, Mark Weaver wrote:
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
Is there anything in /etc/hosts.{allow,deny} that would block traffic to the portmap on the server?
Paul Heinlein wrote:
On 04/25/2005 03:22 AM, Mark Weaver wrote:
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
Is there anything in /etc/hosts.{allow,deny} that would block traffic to the portmap on the server?
not a thing. I've checked everywhere I can think of. The really strange thing is that apart from the /etc/exports file there doesn't appear to be ANY config files for NFS. That is just plain weird.
No Firewall No SELinux No Hosts Deny entries
Its as if it just decided it didn't want to work any more - it had been working flawlessly for many months.
On Mon, 2005-04-25 at 20:02 -0400, Mark Weaver wrote:
Paul Heinlein wrote:
On 04/25/2005 03:22 AM, Mark Weaver wrote:
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
Is there anything in /etc/hosts.{allow,deny} that would block traffic to the portmap on the server?
not a thing. I've checked everywhere I can think of. The really strange thing is that apart from the /etc/exports file there doesn't appear to be ANY config files for NFS. That is just plain weird.
No Firewall No SELinux No Hosts Deny entries
Its as if it just decided it didn't want to work any more - it had been working flawlessly for many months.
Silly question, but are portmapper, mountd, lockd running? Has the machine been rebooted recently (I have *never* forgotten to do a chckonfig foo on .. after doing a service foo start and having it run, only to be unpleasantly surprised on a reboot). Have you restarted the nfsd service?
Does rpcinfo -p server return sane results?
Sean O'Connell wrote:
On Mon, 2005-04-25 at 20:02 -0400, Mark Weaver wrote:
Paul Heinlein wrote:
On 04/25/2005 03:22 AM, Mark Weaver wrote:
yeah... there's something strange going on with the server because the share can't be mounted from any other machine either.
Is there anything in /etc/hosts.{allow,deny} that would block traffic to the portmap on the server?
not a thing. I've checked everywhere I can think of. The really strange thing is that apart from the /etc/exports file there doesn't appear to be ANY config files for NFS. That is just plain weird.
No Firewall No SELinux No Hosts Deny entries
Its as if it just decided it didn't want to work any more - it had been working flawlessly for many months.
Silly question, but are portmapper, mountd, lockd running? Has the machine been rebooted recently (I have *never* forgotten to do a chckonfig foo on .. after doing a service foo start and having it run, only to be unpleasantly surprised on a reboot). Have you restarted the nfsd service?
Does rpcinfo -p server return sane results?
yep... all the NFS regulars are running. Here are the results from "rpcinfo -p"
rpcinfo -p 192.168.0.4 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 1024 status 100024 1 tcp 1024 status 100021 1 udp 1025 nlockmgr 100021 3 udp 1025 nlockmgr 100021 4 udp 1025 nlockmgr 100021 1 tcp 1029 nlockmgr 100021 3 tcp 1029 nlockmgr 100021 4 tcp 1029 nlockmgr 100011 1 udp 950 rquotad 100011 2 udp 950 rquotad 100011 1 tcp 953 rquotad 100011 2 tcp 953 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 989 mountd 100005 1 tcp 992 mountd 100005 2 udp 989 mountd 100005 2 tcp 992 mountd 100005 3 udp 989 mountd 100005 3 tcp 992 mountd
-
Mark Weaver -
Paul Heinlein -
Plant, Dean -
Sean O'Connell -
Ted Kaczmarek