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

[Ryan Richter <ryan@tau.solarneutrino.net>]

On Sat, Dec 17, 2005 at 02:28:19PM -0500, Trond Myklebust wrote:
> 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?

Nope.

$ ps -ef|grep lock
root        77     5  0 Nov20 ?        00:00:00 [kblockd/0]
foo       6811  6800  0 14:29 pts/0    00:00:00 grep -E lock

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

Er... sort of?

# netstat -ap | grep 32768
udp    11144      0 *:32768                 *:*                                -                   
I'm not sure what that means...  lsof|grep 32768 returns nothing.

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

Not that I know of.

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

Nope, that file contains a 0.  I can't think of anything that would be
changing parameters like this.

There are several identical workstations like this, and all the ones
that are used regularly have lost their lockd.  There's one that's
located in an inconvenient place and nobody ever uses it - this one
still has lockd running.

Thanks,
-ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/