topic Re: NFS mount error "pmap_getmaps rpc problem..." in Operating System - Linux

NFS mount error "pmap_getmaps rpc problem..."

Debbie Fleith — Fri, 23 Jan 2009 18:29:08 GMT

When I issue the following mount command from IP 172.16.40.25 - a RH 3 server, I receive this error:
mount 172.16.40.40:/u /mnt/u
Error: pmap_getmaps rpc problem: RPC: Unable to receive; errno = No route to host
mount: RPC: Remote system error - No route to host

I have /mnt/u created on 172.16.40.25

On 172.16.40.40 (a RH 5 server), my /etc/exports file shows:
/u 172.16.40.25(ro)
/u2 172.16.40.25(ro)
/dtx 172.16.40.25(ro)
/v 172.16.40.25(ro)

I have confirmed that nfs was listed in /proc/filesystems as "nodev nfs" on 172.16.40.25 and rpc.rquotad, rpc.mountd and portmap are running.

Any help on this will be assigned points and be much appreciated.

Re: NFS mount error "pmap_getmaps rpc problem..."

Ivan Ferreira — Fri, 23 Jan 2009 19:09:47 GMT

Ensure that your netmask configuration is correct and you don't have any extrange route in your routing table for both servers.

Please provide the output of the following commands on the RH 3 Server.

ping 172.16.40.40
rpcinnfo -p 172.16.40.40
showmount -e 172.16.40.40

And on the RH 5 server:

ping 172.16.40.25
service iptables status
getenforce

Re: NFS mount error "pmap_getmaps rpc problem..."

Debbie Fleith — Fri, 23 Jan 2009 20:39:11 GMT

From RH3 server at 172.16.40.25:
1. PING 172.16.40.40 (172.16.40.40) 56(84) bytes of data.
64 bytes from 172.16.40.40: icmp_seq=0 ttl=64 time=0.470 ms
64 bytes from 172.16.40.40: icmp_seq=1 ttl=64 time=0.169 ms
Ã²
--- 172.16.40.40 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1011ms
rtt min/avg/max/mdev = 0.169/0.319/0.470/0.151 ms, pipe 2
-------
2. rpcinfo -p 172.16.40.40
rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host
-------
3. showmount -e 172.16.40.40
mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive
========
On RH 5 server at 172.16.40.40:
ping 172.16.40.25
PING 172.16.40.25 (172.16.40.25) 56(84) bytes of data.
64 bytes from 172.16.40.25: icmp_seq=1 ttl=64 time=0.244 ms
64 bytes from 172.16.40.25: icmp_seq=2 ttl=64 time=0.235 ms
64 bytes from 172.16.40.25: icmp_seq=3 ttl=64 time=0.283 ms
Ã²
--- 172.16.40.25 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
------
2. service iptables status
Table: filter
Chain INPUT (policy ACCEPT)
num target prot opt source destination
1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT)
num target prot opt source destination
1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
num target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
num target prot opt source destination
1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255

3 ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0
4 ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0
5 ACCEPT udp -- 0.0.0.0/0 224.0.0.251 udp dpt:5353
6 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:631
7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:631
8 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,
ESTABLISHED
9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:21
10 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:25
11 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:22
12 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp
dpt:137
13 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp
dpt:138
14 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:139
15 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:445
16 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:443
17 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:23
18 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:80
19 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:110
20 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp
dpt:631
21 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with ic
mp-host-prohibited

-------
3. getenforce
Disabled

Re: NFS mount error "pmap_getmaps rpc problem..."

Ivan Ferreira — Sat, 24 Jan 2009 18:07:45 GMT

From the commands output, I think that the problem is caused by the firewall enabled on the RH 5 server.

If you really need the firewall enabled there, ensure that you allow incoming traffic to the portmap service and other ports required by NFS (don't remember exactly).

If you don't need the firewall, run:

service iptables stop
chkconfig iptables off

You should stop your firewall anyway to diagnose the problem, use the service iptables stop command to do that.

Re: NFS mount error "pmap_getmaps rpc problem..."

Debbie Fleith — Tue, 27 Jan 2009 18:13:48 GMT

I was able to get one of my filesystems mounted on .25 now that I disabled the firewall on .40 yesterday. At that time, I could cd to /mnt/u and see the files from that remote system.

However, today the server at .25 seems to hang when i try to cd to /mnt/u.

Here is what my mount command shows now:
172.16.40.40:/u on /mnt/u type nfs (rw,addr=172.16.40.40)

But when I cd /mnt/u, nothing comes back and my session appears hung. I see no errors in /var/log/messages from a different session on .25. Any ideas?