* mount: RPC: Timed out but should not.
@ 2003-07-15 20:32 FuturaHost.Com's Support
2003-07-15 20:40 ` mount: RPC: Timed out but should not. more about FuturaHost.Com's Support
0 siblings, 1 reply; 2+ messages in thread
From: FuturaHost.Com's Support @ 2003-07-15 20:32 UTC (permalink / raw)
To: 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 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 :-)
Pablo Povarchik
--
FuturaHost.Com Support
http://futurahost.com/
24/7/365 Toll Free Support: 800592259
24/7/365 Support: +39 0461 592710
FAX: +39 0461 592056
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: mount: RPC: Timed out but should not. more about
2003-07-15 20:32 mount: RPC: Timed out but should not FuturaHost.Com's Support
@ 2003-07-15 20:40 ` FuturaHost.Com's Support
0 siblings, 0 replies; 2+ messages in thread
From: FuturaHost.Com's Support @ 2003-07-15 20:40 UTC (permalink / raw)
To: nfs
I can see in the messages file:
Jul 15 22:21:33 mars rpc.mountd: refused mount request from
Ðß^RBÐß^RBø(^F^Hø(^F^Hàß^RBàß^RBèß^RBèß^RBðß^RBðß^RBøß^RBøß^RB for /
(/): no export entry
what is this??
Thanks, really
Pablo
El mar, 15 de 07 de 2003 a las 22:32, FuturaHost.Com's Support escribió:
> 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 :-)
>
>
>
> Pablo Povarchik
--
FuturaHost.Com Support
http://futurahost.com/
24/7/365 Toll Free Support: 800592259
24/7/365 Support: +39 0461 592710
FAX: +39 0461 592056
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-07-15 20:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-15 20:32 mount: RPC: Timed out but should not FuturaHost.Com's Support
2003-07-15 20:40 ` mount: RPC: Timed out but should not. more about FuturaHost.Com's Support
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.