Re: lockd: couldn't create RPC handle for (host)

[Trond Myklebust <trond.myklebust@fys.uio.no>]

On Sat, 2005-12-17 at 02:02 -0500, Ryan Richter wrote:
> > > There's no filtering between the two.  I get this on the machine itself:
> > > $ rpcinfo -u localhost 100021
> > > rpcinfo: RPC: Timed out
> > > program 100021 version 0 is not available
> > > zsh: exit 1     rpcinfo -u localhost 100021
> > > 
> > > There's no lockd process running on this client machine anymore.
> > 
> > ...yet the client still has the partition mounted, and isn't using the
> > -onolock option? That sounds weird.
> 
> There are lots of nfs mounts, the root is ro nolock, but the trouble is
> with the home directories which are rw lock.  Everything is still
> mounted, I can ssh in fine etc.  The problem is with people using kde -
> it tries to lock some file in the home directory during the login
> process and hangs.

So what do you mean when you say that there is "no lockd process
running" on the client?

Is it not appearing in the output of 'ps -ef' either?

Is anything at all listening on port 32768 on 'jacquere'? (check using
'netstat -ap | grep 32768').

Could anything be playing around with the 'pmap_set' utility so as to
corrupt portmap?

Are you perhaps setting /proc/sys/fs/nfs/nlm_udpport and/or the kernel
parameter nfs.nlm_udpport? If so, to what?

Cheers,
  Trond