From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: lockd: couldn't create RPC handle for
Date: Thu, 27 Apr 2006 10:10:31 -0400
Message-ID: <1146147031.8142.3.camel@lade.trondhjem.org>
References: <215ff4410604270204x3e7cf525u8d019e4d1b1ac9d0@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: Chris Fanning <christopher.fanning@gmail.com>
In-Reply-To: <215ff4410604270204x3e7cf525u8d019e4d1b1ac9d0@mail.gmail.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

On Thu, 2006-04-27 at 11:04 +0200, Chris Fanning wrote:
> Hello all,
> 
> I'm new aboard and, although I've been using nfs for some time now,
> I've never really stopped to learn much about it.
> Now I've got a problem.
> 
> I'm exporting homes.
> on the server (192.168.172.30)
> /home client(rw,no_root_squash,sync)
> 
> on the client(192.168.172.31) fstab
> server:/home      /home           nfs     tcp,rw          0       0
> 
> This seemed to be working ok until I upgraded the kernel on the nfs
> server to 2.6.16
> 
> Now, when a users opens his X session the nfs client console says
> lockd: couldn't create RPC handle for 192.168.172.30
> 
> I have found a thread on this list not long ago so I tried followed it.
> Below, I answer some of the same questions asked on that thread hoping
> this will give some clues.
> 
> >Does 'rpcinfo -u w.x.y.z 100021' work from the server?
> 
> rpcinfo -u 192.168.172.31 100021
> 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
> 
> on the client (192.168.172.31) console is says
> svc: unknown version (0)
> svc: unknown version (2)
> 
> > Is anything at all listening on port 32768 on '192.168.172.31'?
> netstat -ap | grep 32768
> udp        0      0 *:32768                 *:*
> 
> on client
> ps -ef|grep lock
> root      1152     1  0 10:05 ?        00:00:00 [lockd]
> 
> /home is mounted and I can use it.
> But why does the nfs client console fill up with these "lockd:
> couldn't create RPC handle for 192.168.172.30" ?

The message indicates that your client can't access the lockd on the
server. IOW, you really want to try the same tests that you performed
above in reverse (i.e. from the client to the server).

Cheers,
  Trond


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs