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
^^^ happens when running the command "service netfs restart[start]"
I've researched this exaustively on Google and have come up with nuttin. what makes no sense at all to me is that it worked perfectly before on my previous centos 4 installation and has only developed this behavior since reinstalling and upgrading KDE to KDE-3.4 although I can't see what was in there that might have affected netfs/nfs share mounting since the other two shares from the Mandrake server do work.
Any help will be greatly appreciated.
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?
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)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
also try using nfsver=2 to the fstab or nfsver=3
J
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? |
****************************************************************************** The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please note that emails to, from and within RTÉ may be subject to the Freedom of Information Act 1997 and may be liable to disclosure. ******************************************************************************
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
On 4/24/05, Paul Heinlein heinlein@madboa.com wrote:
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
I don't know about current systems, but we have a lot of RH9 desktops at work, and they unformly break (including kernel oops) with "sync"; we use "async" in all our exports.
Paul Heinlein wrote:
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
After adding those options to the list the results are the same. Although I'm curious what "root_squash" does. If my assumption is correct it prevents root user on the client machine from authenticating, yes?
On 4/24/05, Mark Weaver mdw1982@mdw1982.com wrote:
Paul Heinlein wrote:
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
After adding those options to the list the results are the same. Although I'm curious what "root_squash" does. If my assumption is correct it prevents root user on the client machine from authenticating, yes?
-- Mark
Paid for by Penguins against modern appliances(R) Linux User Since 1996 Powered by Mandrake Linux 8.2, 10.0 & RHEL 4 _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
from exports manpage:
root_squash Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not apply to any other uids that might be equally sensitive, such as user bin.
and ...
no_root_squash Turn off root squashing. This option is mainly useful for diskless clients.
On Sun, 2005-04-24 at 10:43 -0400, Mark Weaver wrote:
Paul Heinlein wrote:
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
After adding those options to the list the results are the same.
Have you ruled out iptables on either the client or the server or both? If you stop iptables on the client (/sbin/service iptables stop), does the nfs mount work?
I find on my NFS clients, that i need to allow connections to port 111 and also to higher level tcp ports (assuming you are doing NFS over tcp) --destination-ports 32768:65535.
Sean
Sean O'Connell wrote:
On Sun, 2005-04-24 at 10:43 -0400, Mark Weaver wrote:
Paul Heinlein wrote:
On 04/24/2005 06:54 AM, Mark Weaver wrote:
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)
In the server's /etc/exports, try adding "insecure" to the general option list, e.g.,
/foo/bar 192.168.10.0/24(rw,root_squash,insecure,sync)
The nfs client that ships with CentOS 4 uses a port number higher than 1024 by default, which isn't what most Linux systems expect.
After adding those options to the list the results are the same.
Have you ruled out iptables on either the client or the server or both? If you stop iptables on the client (/sbin/service iptables stop), does the nfs mount work?
I find on my NFS clients, that i need to allow connections to port 111 and also to higher level tcp ports (assuming you are doing NFS over tcp) --destination-ports 32768:65535.
Sean
neither the client or the server in question is running any type of firewall. They're both behind a gateway machine that provides firewalling for the entire LAN. I finally became so disgusted with trying to find out what was going on that I simply reloaded the workstation with a fresh install of CentOS 4. While that was loading I tried mounting the exported share from another machine on the LAN and received the same results. so that pretty much tells me the problem is definitely on the server. That server is an FC3 machine and is very close to being converted to a CentOS machine because I'm very quickly becoming disenchanted with Fedora Core 3.
My next step before reloading that machine is to get nfs reinstalled and working. baring that its a reload for certain.
-
Collins Richey -
John Moylan -
Mark Weaver -
Noah Dain -
Paul Heinlein -
Sean O'Connell