[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2097
  • Last Modified:

RPC binf failure-time out NFS problem

i am trying to share file in linux and mount it on solaris box
  in /etc/pxports file i have added following entries  (server ip 151.108.114.141)

 /home/santhosh    151.108.140.61 (rw) 152.159.39.181 (rw)

  when i execute followinf command on client machines
    on 151.108.140.61 and 152.159.39.181
        dfshares 151.100.114.141
          nfs dfshares:151.108.114.141: RPC: Rpcbind failure - RPC: Timed out

i can able to ping both client form servers and vice versa

i can able to mount shared directory( /home/santhosh) on the clinet 151.108.114.143(Note server and client are in same subnet 151.108.114.x )

  what could be the issue?




on server side:151.108.114.141
   rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  32768  status
    100024    1   tcp  32769  status
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32771  nlockmgr
    100021    3   tcp  32771  nlockmgr
    100021    4   tcp  32771  nlockmgr
    391002    2   tcp  47359  sgi_fam
    100011    1   udp    967  rquotad
    100011    2   udp    967  rquotad
    100011    1   tcp    970  rquotad
    100011    2   tcp    970  rquotad
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100005    1   udp    981  mountd
    100005    1   tcp    984  mountd
    100005    2   udp    981  mountd
    100005    2   tcp    984  mountd
    100005    3   udp    981  mountd
    100005    3   tcp    984  mountd
client machine : 151.108.114.141
     rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
    100001    2   udp  32772  rstatd
    100001    3   udp  32772  rstatd
    100001    4   udp  32772  rstatd
    100229    1   tcp  32771  metad
    100229    2   tcp  32771  metad
    100422    1   tcp  32772
    100024    1   udp  32774  status
    100024    1   tcp  32773  status
    100133    1   udp  32774
    100133    1   tcp  32773
    100021    1   udp   4045  nlockmgr
    100021    2   udp   4045  nlockmgr
    100021    3   udp   4045  nlockmgr
    100021    4   udp   4045  nlockmgr
    100021    1   tcp   4045  nlockmgr
    100021    2   tcp   4045  nlockmgr
    100021    3   tcp   4045  nlockmgr
    100021    4   tcp   4045  nlockmgr
    300598    1   udp  32779
    300598    1   tcp  32783
 805306368    1   udp  32779
 805306368    1   tcp  32783
    100249    1   udp  32780
    100249    1   tcp  32784
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100005    1   udp  32863  mountd
    100005    2   udp  32863  mountd
    100005    3   udp  32863  mountd
    100005    1   tcp  33168  mountd
    100005    2   tcp  33168  mountd
    100005    3   tcp  33168  mountd

Open in new window

0
sants_pp
Asked:
sants_pp
  • 2
1 Solution
 
bummerlordCommented:
This seems like a network issue, or possibly RPC version incompatibility (would expect another error message though). The machine (151.108.114.143) that is able to mount the share, is that a Linux box as well?

Check that there are no odd iptables rules in the linux box that prevent certain protocols from outside the same subnet (you may have installed this machine and know there are none, but as I don't know that I will include the possibillity)

# iptables-save

Check if there any firewalls or access-lists in routers separating the NFS server from the networks where you are unable to mount the share? If there are, you should verify what ports/protocols are accepted with the firewall/network administrator (who will also be able to parse the firewall logs and tell if there are blocked packets to/from the hosts in question)

If you can't get hold of the firewall administrator, you can capture network traffic on both ends, and try to figure out what packet, and in what direction, is not reaching through.

linux# tcpdump -s0 -w rawoutput.pcap -i eth0 -n host <solarisbox IP>

solaris# snoop -r -s0 -o rawoutput.snoop host <linuxbox IP>

while running the above do;
otherterminalonsolaris# dfshare 151.108.140.61
linux# rpcinfo -p <solaris IP>

then terminate tcpdump and snoop transfer the dump files to somewhere you got ethereal / wireshark and open them to do some investigation.. could be time consuming depending on what you know about networking and how much data is exposed to the network interfaces. But it should
If the network is normally very quiet you could run the snoop/tcpdump without "-w" and "-o" to have a brief packet description printed direcly in the terminal.

If you find that something in the network prohibits NFS traffic between your machines, then the solution is "simply" to make sure that that obstacle is removed :-) (may involve buying your network administration a bottle of carefully aged liquids)
0
 
Brian UtterbackPrinciple Software EngineerCommented:
You should also try running the command "rpcinfo -p <linuxbox IP>" on the Solaris client.
0
 
sants_ppAuthor Commented:
Hi ,
   i followed your steps and ran tcpdump command .i exeuted foolowing commands on other terminel while running tcpdump commnad
        otherterminalonsolaris# dfshare Linux ip
                                             # rpcinfo -p linux ip
                                linux# rpcinfo -p <solaris IP>

when i execute rpcinfo -p solairs ip   on linux machine  i can get output.but when i exeute rpcinfo -p linuxip on solaris machine i cannot get any outputs.it hungs.

   i cannot understand tcpdump output .help me to understand tcpdump output.what do you think what could be the exact issue.
   servers in the same segment (151.108.114.x) can able to mount the share regardless of linux or solaris.but servers in the diff segment cannot able to mount share.how can i resolve the issue.

please refer outputs

   
followinf are tcpdump outputs form Linux to Solris
Linux ip:151.108.114.141  (nfs server)
solaris server:151.108.140.61 (client)
 
10:20:06.072850 151.108.114.141.910 > 151.108.140.61.111: S 2443577446:2443577446(0) win 5840 <mss 1460,sackOK,timestamp 2938219497 0,nop,wscale 0> (DF)
10:20:06.073742 151.108.140.61.111 > 151.108.114.141.910: S 631993638:631993638(0) ack 2443577447 win 49232 <nop,nop,timestamp 2938225949 2938219497,mss 1460,nop,wscale 0,nop,nop,sackOK> (DF)
10:20:06.073762 151.108.114.141.910 > 151.108.140.61.111: . ack 1 win 5840 <nop,nop,timestamp 2938219497 2938225949> (DF)
10:20:06.073818 151.108.114.141.910 > 151.108.140.61.111: P 1:45(44) ack 1 win 5840 <nop,nop,timestamp 2938219497 2938225949> (DF)
10:20:06.074367 151.108.140.61.111 > 151.108.114.141.910: . ack 45 win 49188 <nop,nop,timestamp 2938225949 2938219497> (DF)
10:20:06.075366 151.108.140.61.111 > 151.108.114.141.910: P 1:913(912) ack 45 win 49232 <nop,nop,timestamp 2938225949 2938219497> (DF)
10:20:06.075373 151.108.114.141.910 > 151.108.140.61.111: . ack 913 win 7296 <nop,nop,timestamp 2938219498 2938225949> (DF)
10:20:06.077575 151.108.114.141.910 > 151.108.140.61.111: F 45:45(0) ack 913 win 7296 <nop,nop,timestamp 2938219498 2938225949> (DF)
10:20:06.078364 151.108.140.61.111 > 151.108.114.141.910: . ack 46 win 49232 <nop,nop,timestamp 2938225949 2938219498> (DF)
10:20:06.078378 151.108.140.61.111 > 151.108.114.141.910: F 913:913(0) ack 46 win 49232 <nop,nop,timestamp 2938225949 2938219498> (DF)
10:20:06.078389 151.108.114.141.910 > 151.108.140.61.111: . ack 914 win 7296 <nop,nop,timestamp 2938219498 2938225949> (DF)
 
 
following are tcpdump form solaris to linux
   1   0.00000 ny1bo200stgsa -> 151.108.114.141 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=TCP
  2  90.86546 151.108.114.141 -> ny1bo200stgsa TCP D=111 S=910 Syn Seq=2443577446 Len=0 Win=5840 Options=<mss 1460,sackOK,tstamp 2938219497 0,nop,wscale 0>
  3   0.00013 ny1bo200stgsa -> 151.108.114.141 TCP D=910 S=111 Syn Ack=2443577447 Seq=631993638 Len=0 Win=49232 Options=<nop,nop,tstamp 2938225949 2938219497,mss 1460,nop,wscale 0,nop,nop,sackOK>
  4   0.00061 151.108.114.141 -> ny1bo200stgsa TCP D=111 S=910 Ack=631993639 Seq=2443577447 Len=0 Win=5840 Options=<nop,nop,tstamp 2938219497 2938225949>
  5   0.00002 151.108.114.141 -> ny1bo200stgsa PORTMAP C DUMP
  6   0.00003 ny1bo200stgsa -> 151.108.114.141 TCP D=910 S=111 Ack=2443577491 Seq=631993639 Len=0 Win=49188 Options=<nop,nop,tstamp 2938225949 2938219497>
  7   0.00083 ny1bo200stgsa -> 151.108.114.141 PORTMAP R DUMP 44 map(s) found
  8   0.00060 151.108.114.141 -> ny1bo200stgsa TCP D=111 S=910 Ack=631994551 Seq=2443577491 Len=0 Win=7296 Options=<nop,nop,tstamp 2938219498 2938225949>
  9   0.00249 151.108.114.141 -> ny1bo200stgsa TCP D=111 S=910 Fin Ack=631994551 Seq=2443577491 Len=0 Win=7296 Options=<nop,nop,tstamp 2938219498 2938225949>
 10   0.00003 ny1bo200stgsa -> 151.108.114.141 TCP D=910 S=111 Ack=2443577492 Seq=631994551 Len=0 Win=49232 Options=<nop,nop,tstamp 2938225949 2938219498>
 11   0.00005 ny1bo200stgsa -> 151.108.114.141 TCP D=910 S=111 Fin Ack=2443577492 Seq=631994551 Len=0 Win=49232 Options=<nop,nop,tstamp 2938225949 2938219498>
 12   0.00041 151.108.114.141 -> ny1bo200stgsa TCP D=111 S=910 Ack=631994552 Seq=2443577492 Len=0 Win=7296 Options=<nop,nop,tstamp 2938219498 2938225949>
 13  22.32138 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>
 14   3.36099 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>
 15   6.74998 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>
 16  13.50005 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>
 17  26.99994 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>
 18  53.99991 ny1bo200stgsa -> 151.108.114.141 TCP D=111 S=740 Syn Seq=638076651 Len=0 Win=49640 Options=<mss 1460,nop,nop,sackOK>

Open in new window

0
 
Brian UtterbackPrinciple Software EngineerCommented:
Now, that's interesting. The first attempt by the Solaris system to contact the Linux system's rpcbind succeeds, but the
second attempt hangs. Since there are no reset packets, that indicates that rpcbind on the Linux system is running,
but since there are no replies to the Syn packets, it seems like the rpcbind's listen queue is full. In any case, the problem
seems to be that the rpcbind on the Linux system is not responding to rpcbind requests. You need to look at what
is going on on the Linux box. Could there be any IP filtering going on there?
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now