Arch Linux

fivre

Member

Registered: 2007-04-17

Posts: 97

NFS No route to host

I've installed NFS as per the wiki article, but I'm getting

mount: mount to NFS server 'nrtb' failed: System Error: No route to host.

when I try to start it, even though my hosts.allow is correct and I'm not running iptables or anything of the sort. What's wrong?

mico

Member

From: Slovenia

Registered: 2004-02-08

Posts: 247

Re: NFS No route to host

Is the NFS server pc up and running at all? Maybe DNS is giving problems, try with numeric address. Can you ping the same address?

rhfrommn

Member

From: Minnesota

Registered: 2005-01-13

Posts: 99

Re: NFS No route to host

Yes, if you get this message NFS is up and running fine and attempting the mount, but there is a network problem preventing it.  Check your routing setup and that the server is up and running.  The suggestion to try pinging the server both by name and address is a good one.  Maybe try traceroute as well if the network is more complex than the server and client both being on the same subnet.

fivre

Member

Registered: 2007-04-17

Posts: 97

Re: NFS No route to host

Nope. Both those are fine. I can do other network things (ssh, scp, etc.) perfectly fine. Just not NFS.

rhfrommn

Member

From: Minnesota

Registered: 2005-01-13

Posts: 99

Re: NFS No route to host

That is surprising.  However, when the obvious fix doesn't work I guess try some less obvious things.  Here are a few wild guesses to try.

1.  Kill/restart NFS on your client and server then try again.  Or just reboot both.  Maybe one of the daemons was running but had a problem that restarting it could clear.

2.  Try the mount using the IP address instead of server name to see if it is an issue with NFS using DNS.  Like this:
mount 192.168.xxx.xxx:/host/directory /mountdir
If that works you can just use it that way, or investigate why your NFS daemon can't resolve using DNS properly.

3.  Add the server's name and IP to /etc/hosts on the client and vice versa if it isn't already there then try again.  That just does an end-run around the DNS issue if one exists.

4.  Make sure NFS is running as a server on the server, and not just client.  I know in Solaris there are 4 processes that must be running for an NFS server, but only 2 are needed for a client.  I believe it is similar in Arch.  Maybe the server isn't running *all* the needed processes.

That's all my brainstorming can come up with.  Good luck.

fivre

Member

Registered: 2007-04-17

Posts: 97

Re: NFS No route to host

Still no luck.

I can't rpcinfo from the client either:

root@nrte: /home/fivre $ rpcinfo -p nrtb
rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host

Other stuff:

root@nrtb: /home/fivre $ cat /etc/hosts.allow 
#
# /etc/hosts.allow
#
sshd : 137.22.
#nfsd : 137.22.
#portmap : 137.22.
#mountd : 137.22. 
nfsd: ALL
portmap: ALL
mountd: ALL

root@nrtb: /home/fivre $ cat /etc/exports 
# /etc/exports
#
# See exports(5) for a description.

# use exportfs -arv to reread
#/export    192.168.1.10(rw,no_root_squash)

#/mnt/net 137.22.*(rw,sync,all_squash,anonuid=99,anongid=99) ; Read-write access to all clients from 137.22.1.1 to 137.22.255.255 
/mnt/net 137.22.226.140(rw,sync,all_squash,anonuid=99,anongid=99)
/mnt/net 137.22.3.33(rw,sync,all_squash,anonuid=99,anongid=99)

mico

Member

From: Slovenia

Registered: 2004-02-08

Posts: 247

Re: NFS No route to host

So as I understand, when typing commands from nfs client machine, you get something like (suppose your nfs server has numerical address 137.22.226.14):

$ ping 137.22.226.14
PING 137.22.226.14 (137.22.226.14) 56(84) bytes of data.
64 bytes from 137.22.226.14: icmp_seq=1 ttl=64 time=0.608 ms
64 bytes from 137.22.226.14: icmp_seq=2 ttl=64 time=0.591 ms
64 bytes from 137.22.226.14: icmp_seq=3 ttl=64 time=0.570 ms

--- 192.168.2.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.570/0.589/0.608/0.032 ms

$ rpcinfo -p 137.22.226.14
rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host

This is weird indeed.

My /etc/hosts.allow:

portmap: 192.168.1.1
lockd:   192.168.1.1
rquotad: 192.168.1.1
statd:   192.168.1.1
mountd:  192.168.1.1

You could add lockd, rquotad and statd, then try again, it can't hurt trying.

fivre

Member

Registered: 2007-04-17

Posts: 97

Re: NFS No route to host

No luck

rhfrommn

Member

From: Minnesota

Registered: 2005-01-13

Posts: 99

Re: NFS No route to host

Try posting the output of "netstat -r".  Is there a vaild default route?

Also, try "host nrtb" from your client, see if it gives back the correct numeric address.  That means your IP address resolution is ok if it works and then you definately must have some kind of routing problem.