mount: RPC: Timed out - not a newbie - NFS

This is a discussion on mount: RPC: Timed out - not a newbie - NFS ; Hello all From the client: [root@beryllium bin]# iptables -L -n (output abreviated) ACCEPT tcp -- ip.of.the.client 0.0.0.0/0 tcp ACCEPT tcp -- ip.of.the.server 0.0.0.0/0 tcp ACCEPT udp -- ip.of.the.client 0.0.0.0/0 udp ACCEPT udp -- ip.of.the.server 0.0.0.0/0 udp [root@beryllium bin]# rpcinfo -p ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: mount: RPC: Timed out - not a newbie

  1. mount: RPC: Timed out - not a newbie


    Hello all

    From the client:
    [root@beryllium bin]# iptables -L -n (output abreviated)
    ACCEPT tcp -- ip.of.the.client 0.0.0.0/0 tcp
    ACCEPT tcp -- ip.of.the.server 0.0.0.0/0 tcp
    ACCEPT udp -- ip.of.the.client 0.0.0.0/0 udp
    ACCEPT udp -- ip.of.the.server 0.0.0.0/0 udp
    [root@beryllium bin]# rpcinfo -p server
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100011 1 udp 770 rquotad
    100011 2 udp 770 rquotad
    100005 1 udp 778 mountd
    100005 1 tcp 781 mountd
    100005 2 udp 778 mountd
    100005 2 tcp 781 mountd
    100005 3 udp 778 mountd
    100005 3 tcp 781 mountd
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100021 1 udp 33829 nlockmgr
    100021 3 udp 33829 nlockmgr
    100021 4 udp 33829 nlockmgr
    [root@beryllium bin]# rpcinfo -u client nfs
    program 100003 version 2 ready and waiting
    program 100003 version 3 ready and waiting
    [root@beryllium bin]# rpcinfo -u client mountd
    program 100005 version 1 ready and waiting
    program 100005 version 2 ready and waiting
    program 100005 version 3 ready and waiting
    [root@beryllium bin]# rpcinfo -u client nlockmgr
    program 100021 version 1 ready and waiting
    rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 4
    program 100021 version 2 is not available
    program 100021 version 3 ready and waiting
    program 100021 version 4 ready and waiting
    [root@beryllium bin]#

    From the server:

    [root@mars service]# iptables -L -n (output abreviated)
    ACCEPT tcp -- clientipaddr 0.0.0.0/0 tcp
    ACCEPT udp -- clientipaddr 0.0.0.0/0 udp
    [root@mars service]# rpcinfo -p
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100011 1 udp 770 rquotad
    100011 2 udp 770 rquotad
    100005 1 udp 778 mountd
    100005 1 tcp 781 mountd
    100005 2 udp 778 mountd
    100005 2 tcp 781 mountd
    100005 3 udp 778 mountd
    100005 3 tcp 781 mountd
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100021 1 udp 33829 nlockmgr
    100021 3 udp 33829 nlockmgr
    100021 4 udp 33829 nlockmgr
    [root@mars service]# rpcinfo -u localhost nfs
    program 100003 version 2 ready and waiting
    program 100003 version 3 ready and waiting
    [root@mars service]# rpcinfo -u localhost mountd
    program 100005 version 1 ready and waiting
    program 100005 version 2 ready and waiting
    program 100005 version 3 ready and waiting
    [root@mars service]# rpcinfo -u localhost nlockmgr
    program 100021 version 1 ready and waiting
    rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 4
    program 100021 version 2 is not available
    program 100021 version 3 ready and waiting
    program 100021 version 4 ready and waiting
    [root@mars service]#



    Here goes the funny part:
    [root@beryllium bin]# /bin/mount -t nfs -o,hard mars:/ /mnt/nfs
    mount: RPC: Timed out
    [root@beryllium bin]#

    But, when im trying to mount from the client, i see this in the server:

    [root@mars service]# netstat -alnp | grep :53
    udp 0 0 an.ip.onthe.server:34451 anip.on.the.server:53
    ESTABLISHED 13781/rpc.mountd
    udp 0 0 anip.on.the.server:34453 anip.on.the.server:53
    ESTABLISHED 13781/rpc.mountd

    udp 0 0 eth0.ip.on.server:34456 some.ip.querying.dnscache:53
    ESTABLISHED 13781/rpc.mountd
    udp 0 0 eth0.ip.on.server:34457 a-dns.server.onresolv.conf:53
    ESTABLISHED 13781/rpc.mountd


    It's like rpc.mountd is binding hiself on port 53.


    This thing is happening in around 25 servers on our network...

    Obvious to say: PLEASE HELP :-)

    Thanks all
    --
    Pablo Povarchik
    FuturaHost.Com
    Industrial & Business Class ISP

  2. Re: mount: RPC: Timed out - not a newbie

    For troubleshooting, turn off the IP-firewall for a brief time and try mounting it.

    CHeerz,
    Rama
    ===.

    Pablo Povarchik wrote in message news:...
    > Hello all
    >
    > From the client:
    > [root@beryllium bin]# iptables -L -n (output abreviated)
    > ACCEPT tcp -- ip.of.the.client 0.0.0.0/0 tcp
    > ACCEPT tcp -- ip.of.the.server 0.0.0.0/0 tcp
    > ACCEPT udp -- ip.of.the.client 0.0.0.0/0 udp
    > ACCEPT udp -- ip.of.the.server 0.0.0.0/0 udp
    > [root@beryllium bin]# rpcinfo -p server
    > program vers proto port
    > 100000 2 tcp 111 portmapper
    > 100000 2 udp 111 portmapper
    > 100011 1 udp 770 rquotad
    > 100011 2 udp 770 rquotad
    > 100005 1 udp 778 mountd
    > 100005 1 tcp 781 mountd
    > 100005 2 udp 778 mountd
    > 100005 2 tcp 781 mountd
    > 100005 3 udp 778 mountd
    > 100005 3 tcp 781 mountd
    > 100003 2 udp 2049 nfs
    > 100003 3 udp 2049 nfs
    > 100021 1 udp 33829 nlockmgr
    > 100021 3 udp 33829 nlockmgr
    > 100021 4 udp 33829 nlockmgr
    > [root@beryllium bin]# rpcinfo -u client nfs
    > program 100003 version 2 ready and waiting
    > program 100003 version 3 ready and waiting
    > [root@beryllium bin]# rpcinfo -u client mountd
    > program 100005 version 1 ready and waiting
    > program 100005 version 2 ready and waiting
    > program 100005 version 3 ready and waiting
    > [root@beryllium bin]# rpcinfo -u client nlockmgr
    > program 100021 version 1 ready and waiting
    > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 4
    > program 100021 version 2 is not available
    > program 100021 version 3 ready and waiting
    > program 100021 version 4 ready and waiting
    > [root@beryllium bin]#
    >
    > From the server:
    >
    > [root@mars service]# iptables -L -n (output abreviated)
    > ACCEPT tcp -- clientipaddr 0.0.0.0/0 tcp
    > ACCEPT udp -- clientipaddr 0.0.0.0/0 udp
    > [root@mars service]# rpcinfo -p
    > program vers proto port
    > 100000 2 tcp 111 portmapper
    > 100000 2 udp 111 portmapper
    > 100011 1 udp 770 rquotad
    > 100011 2 udp 770 rquotad
    > 100005 1 udp 778 mountd
    > 100005 1 tcp 781 mountd
    > 100005 2 udp 778 mountd
    > 100005 2 tcp 781 mountd
    > 100005 3 udp 778 mountd
    > 100005 3 tcp 781 mountd
    > 100003 2 udp 2049 nfs
    > 100003 3 udp 2049 nfs
    > 100021 1 udp 33829 nlockmgr
    > 100021 3 udp 33829 nlockmgr
    > 100021 4 udp 33829 nlockmgr
    > [root@mars service]# rpcinfo -u localhost nfs
    > program 100003 version 2 ready and waiting
    > program 100003 version 3 ready and waiting
    > [root@mars service]# rpcinfo -u localhost mountd
    > program 100005 version 1 ready and waiting
    > program 100005 version 2 ready and waiting
    > program 100005 version 3 ready and waiting
    > [root@mars service]# rpcinfo -u localhost nlockmgr
    > program 100021 version 1 ready and waiting
    > rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 4
    > program 100021 version 2 is not available
    > program 100021 version 3 ready and waiting
    > program 100021 version 4 ready and waiting
    > [root@mars service]#
    >
    >
    >
    > Here goes the funny part:
    > [root@beryllium bin]# /bin/mount -t nfs -o,hard mars:/ /mnt/nfs
    > mount: RPC: Timed out
    > [root@beryllium bin]#
    >
    > But, when im trying to mount from the client, i see this in the server:
    >
    > [root@mars service]# netstat -alnp | grep :53
    > udp 0 0 an.ip.onthe.server:34451 anip.on.the.server:53
    > ESTABLISHED 13781/rpc.mountd
    > udp 0 0 anip.on.the.server:34453 anip.on.the.server:53
    > ESTABLISHED 13781/rpc.mountd
    >
    > udp 0 0 eth0.ip.on.server:34456 some.ip.querying.dnscache:53
    > ESTABLISHED 13781/rpc.mountd
    > udp 0 0 eth0.ip.on.server:34457 a-dns.server.onresolv.conf:53
    > ESTABLISHED 13781/rpc.mountd
    >
    >
    > It's like rpc.mountd is binding hiself on port 53.
    >
    >
    > This thing is happening in around 25 servers on our network...
    >
    > Obvious to say: PLEASE HELP :-)
    >
    > Thanks all


+ Reply to Thread