* intermitent mount: RPC: Timed - please help
@ 2003-07-16 23:21 FuturaHost.Com's Support
2003-07-18 1:07 ` i insist! " FuturaHost.Com's Support
0 siblings, 1 reply; 3+ messages in thread
From: FuturaHost.Com's Support @ 2003-07-16 23:21 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
--
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 is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* i insist! intermitent mount: RPC: Timed - please help
2003-07-16 23:21 intermitent mount: RPC: Timed - please help FuturaHost.Com's Support
@ 2003-07-18 1:07 ` FuturaHost.Com's Support
2003-07-18 1:26 ` Neil Brown
0 siblings, 1 reply; 3+ messages in thread
From: FuturaHost.Com's Support @ 2003-07-18 1:07 UTC (permalink / raw)
To: nfs
Im posting in the wrong list? Can someone in this list kindly make me
note it and point me to the right one?
Please also note that i tried ALL, and this does not seems like a
portmapper problem
Thanks again
Pablo
El jue, 17 de 07 de 2003 a las 01:21, 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
--
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 is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: i insist! intermitent mount: RPC: Timed - please help
2003-07-18 1:07 ` i insist! " FuturaHost.Com's Support
@ 2003-07-18 1:26 ` Neil Brown
0 siblings, 0 replies; 3+ messages in thread
From: Neil Brown @ 2003-07-18 1:26 UTC (permalink / raw)
To: support3; +Cc: nfs
On July 18, support3@futurahost.com wrote:
>
> Im posting in the wrong list? Can someone in this list kindly make me
> note it and point me to the right one?
No, you are posting to the right list. But there in not guarantee
that you will get a reply. People are busy etc.
When you don't get a reply, it doesn't hurt to send the question
again, so you have done the right thing!!
> > [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
Hmm, you don't seem to be running 'statd', so locking won't work, but
that is not your immediate problem.
> > [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
No statd on the server either.
> >
> >
> >
> > Here goes the funny part:
> > [root@beryllium bin]# /bin/mount -t nfs -o,hard mars:/ /mnt/nfs
> > mount: RPC: Timed out
> > [root@beryllium bin]#
Any logs from mountd? Maybe try 'strace' or 'ltrace' on mountd and
see what it is doing.
> >
> > 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.
> >
But we know (from rpcinfo) that it isn't.
It is more like someone (mountd?) is doing a DNS request and maybe not
getting a reply.
My guess is that mountd gets the request from the client, does a DNS
lookup to verify the request, never gets an answer for some reason,
and so doesn't reply before the client times out.
I suggest checking that DNS lookup is really working on the server.
NeilBrown
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-07-18 1:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-16 23:21 intermitent mount: RPC: Timed - please help FuturaHost.Com's Support
2003-07-18 1:07 ` i insist! " FuturaHost.Com's Support
2003-07-18 1:26 ` Neil Brown
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.