I'm running 5.4-STABLE (about two weeks old), and have just set up an NFS server for the first time. Remote mounts sometimes work fine, and sometimes fail. The symptoms are that "showmount -e" sez showmount: can't do exports rpc and that "rpcinfo -u <host> mountd" often works fine n times in a row, and then stops working, like so: ... Michael-Sperbers-Computer[105] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[106] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[107] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[108] rpcinfo -u matt mountd program 100005 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 100005 version 2 is not available program 100005 version 3 ready and waiting Michael-Sperbers-Computer[109] rpcinfo -u matt mountd rpcinfo: RPC: Timed out program 100005 version 0 is not available>From then on, it'll keep failing.... and, of course, doing it from the machine I really want to be doing it from reliably switches it to failure mode. Any ideas on what I should do? -- Cheers =8-} Mike Friede, V?lkerverst?ndigung und ?berhaupt blabla
Michael Sperber <sperber@informatik.uni-tuebingen.de> wrote:
> I'm running 5.4-STABLE (about two weeks old), and have just set up an
> NFS server for the first time. Remote mounts sometimes work fine, and
> sometimes fail.
>
> The symptoms are that "showmount -e" sez
>
> showmount: can't do exports rpc
>
> and that "rpcinfo -u <host> mountd" often works fine n
times in a row,
> and then stops working, like so:
>
> ...
> Michael-Sperbers-Computer[105] rpcinfo -u matt mountd
> program 100005 version 1 ready and waiting
> rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
> program 100005 version 2 is not available
> program 100005 version 3 ready and waiting
> Michael-Sperbers-Computer[106] rpcinfo -u matt mountd
> program 100005 version 1 ready and waiting
> rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
> program 100005 version 2 is not available
> program 100005 version 3 ready and waiting
> Michael-Sperbers-Computer[107] rpcinfo -u matt mountd
> program 100005 version 1 ready and waiting
> rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
> program 100005 version 2 is not available
> program 100005 version 3 ready and waiting
> Michael-Sperbers-Computer[108] rpcinfo -u matt mountd
> program 100005 version 1 ready and waiting
> rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3
> program 100005 version 2 is not available
> program 100005 version 3 ready and waiting
> Michael-Sperbers-Computer[109] rpcinfo -u matt mountd
> rpcinfo: RPC: Timed out
> program 100005 version 0 is not available
>
> From then on, it'll keep failing.
That looks like your rpcbind(8) process died. Can you
check that with ps? Also, are there any warnings or
errors reported in /var/log/messages?
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"Python is an experiment in how much freedom programmers need.
Too much freedom and nobody can read another's code; too little
and expressiveness is endangered."
-- Guido van Rossum
Michael Sperber <sperber@informatik.uni-tuebingen.de> writes:> I'm running 5.4-STABLE (about two weeks old), and have just set up an > NFS server for the first time. Remote mounts sometimes work fine, and > sometimes fail. > > The symptoms are that "showmount -e" sez > > showmount: can't do exports rpc > > and that "rpcinfo -u <host> mountd" often works fine n times in a row, > and then stops working, like so:Turns out that mountd seems to be trying to do reverse DNS lookups, and when those block, the whole process locks up. I don't understand why, though: the servers listed in /etc/exports are by IP. Any ideas? -- Cheers =8-} Mike Friede, V?lkerverst?ndigung und ?berhaupt blabla
On Thu, 29 Dec 2005, Michael Sperber wrote:> > Michael Sperber <sperber@informatik.uni-tuebingen.de> writes: > >> I'm running 5.4-STABLE (about two weeks old), and have just set up an >> NFS server for the first time. Remote mounts sometimes work fine, and >> sometimes fail. >> >> The symptoms are that "showmount -e" sez >> >> showmount: can't do exports rpc >> >> and that "rpcinfo -u <host> mountd" often works fine n times in a row, >> and then stops working, like so: > > Turns out that mountd seems to be trying to do reverse DNS > lookups, and when those block, the whole process locks up. I don't > understand why, though: the servers listed in /etc/exports are by IP. > Any ideas?NFS is twitchy in a lot of ways, you've found one of them. IME, it's easier all the way around for clients and server to have entries for each other in /etc/hosts. hth, Doug -- This .signature sanitized for your protection