PDA

View Full Version : nfs shares not working



nix4me
28th July 2008, 03:55 AM
i setup a nfs share on Fedora 9 machine and it can't be mounted from a remote CentOS or Debian machines. something is broken. I searched forums and google and found nothing. Any ideas?

The remote machine says System Error: No reoute to host. This is not true. i can ping the F9 machine just fine. The F9 machine can mount other nfs shares, it just the F9 nfs shares are broken.

Any ideas?

Skunk Worx
28th July 2008, 05:32 AM
Off the top of my head :

Is the iptables service running and does it have a hole for nfs?

Is the nfs service running?

Can you mount the share(s) to the localhost (the same machine)?

Are there any nfs related messages in /var/log/messages?

what does the '/usr/sbin/showmount -e localhost' command display?

That's how I'd start...see if anything odd comes up looking through that.

EDIT : it's -e for showmount, not -a...

Skunk Worx
28th July 2008, 05:46 AM
Ah. I didn't realize what a bear it is to get iptables working with NFS. This is most likely your problem. If you need iptables running, you'll have to configure NFS to use a lot of static or limited range ports. See :

http://www.ba.infn.it/calcolo/documenti/NFSServer.html#Firewall

nix4me
28th July 2008, 11:12 PM
Iptables is off. NFS is running. Here is the output of:

[root@localhost etc]# showmount -e localhost
Export list for localhost:
/mnt/fileserver3 192.168.1.102

Everything is fine, accept my lan machines cannot mount them.

Skunk Worx
28th July 2008, 11:56 PM
It looks like you are exporting the share to a single IP address rather than multiple client machines. Is that your intent?

Can you see the share with 'showmount -e' from the host at IP address 192.168.1.102?

Is there anything in the logs of either of these machines (the server or the 192. host) mentioning a problem?


Consider changing the /etc/exports entry to something like :

/mnt/fileserver3 127.0.0.1 192.168.1.0/24

...then see if the localhost server can mount itself (say to a a directory in /tmp) then see if any other hosts on your subnet can mount it, or see it with 'showmount -e (server_ip_address)'

What does

# exportfs -a

...show?

nix4me
29th July 2008, 12:38 AM
It looks like you are exporting the share to a single IP address rather than multiple client machines. Is that your intent?

Can you see the share with 'showmount -e' from the host at IP address 192.168.1.102?

Is there anything in the logs of either of these machines (the server or the 192. host) mentioning a problem?


Consider changing the /etc/exports entry to something like :

/mnt/fileserver3 127.0.0.1 192.168.1.0/24

...then see if the localhost server can mount itself (say to a a directory in /tmp) then see if any other hosts on your subnet can mount it, or see it with 'showmount -e (server_ip_address)'

What does

# exportfs -a

...show?

I configured exports are you recommended.

Showmount from 192.168.1.102 shows this:
[root@nameserver ~]# showmount -e 192.168.1.198
mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive

Nothing in the logs about problems

Mounting locally to /tmp/test works fine

exportfs -a shows nothing

nix4me
29th July 2008, 01:12 AM
fixed,

I was using the 'network' service instead of 'network manager'.

I have no idea why this was causing problems but it was.

Skunk Worx
29th July 2008, 01:50 AM
It's like rpcbind (aka portmap) was ginked up.

I've used either service (network or NetworkManager) and been okay with NFS. Go figure.

Nice catch.