Date: Wed, 13 Nov 2002 17:33:20 -0800 From: Alfred Perlstein <alfred@FreeBSD.org> To: Kris Kennaway <kris@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: rpc.lockd problems Message-ID: <20021114013320.GA50692@elvis.mu.org> In-Reply-To: <20021113164143.C4476@citusc.usc.edu> References: <20021113164143.C4476@citusc.usc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* Kris Kennaway <kris@FreeBSD.org> [021113 16:41] wrote: > A few months ago I posted about rpc.lockd interop problems I am having > between my 5.0 NFS client and a Redhat 7.1 server. Both are running > rpc.lockd, but when I send a lock request to the server it hangs > forever blocked on the /var/run/lock socket. > > tcpdump shows that the lock RPC request is being sent, and answered by > the server. I have the complete tcpdump trace if anyone is > interested. Ah finally! Some useful debug info! It looks like the remote server is not running lockd, or posibly just dropping the lock requests on the floor. Can you get some information about the remote lockd? > 16:27:28.285259 citusc17.usc.edu.641493202 > citusc.usc.edu.nfs: 104 lookup fh Unknown/1 "incoming" > 16:27:28.286179 citusc.usc.edu.nfs > citusc17.usc.edu.641493202: reply ok 232 lookup fh Unknown/1 (DF) > 16:27:28.287395 citusc17.usc.edu.55771 > citusc.usc.edu.sunrpc: udp 56 > 16:27:28.288491 citusc.usc.edu.sunrpc > citusc17.usc.edu.55771: udp 28 (DF) > 16:27:28.289631 citusc17.usc.edu.55772 > citusc.usc.edu.49437: udp 200 > 16:27:28.290549 citusc.usc.edu.49437 > citusc17.usc.edu.55772: udp 28 (DF) Ok, here's where the lock request is done... > Here is what rpc.lockd -d 10 shows: > > Nov 13 16:39:51 citusc17 rpc.lockd: process ID: 10865 > Nov 13 16:39:51 citusc17 rpc.lockd: fh_len 24, fh \01\00\00\02\00\08\00\07\02\00\00\00\40\a0\0e\00\73\09\c6\11\2a\a0\0e\00 > Nov 13 16:39:51 citusc17 rpc.lockd: start 0; len 0; pid 1; type 1; whence 0 > Nov 13 16:39:51 citusc17 rpc.lockd: wait was not set > Nov 13 16:39:51 citusc17 rpc.lockd: lock request: V4: read to 128.125.38.123 > Nov 13 16:39:51 citusc17 rpc.lockd: Found CLIENT* in cache > Nov 13 16:40:11 citusc17 rpc.lockd: process ID: 10865 > Nov 13 16:40:11 citusc17 rpc.lockd: fh_len 24, fh \01\00\00\02\00\08\00\07\02\00\00\00\40\a0\0e\00\73\09\c6\11\2a\a0\0e\00 > Nov 13 16:40:11 citusc17 rpc.lockd: start 0; len 0; pid 1; type 1; whence 0 > Nov 13 16:40:11 citusc17 rpc.lockd: wait was not set > Nov 13 16:40:11 citusc17 rpc.lockd: lock request: V4: read to 128.125.38.123 > Nov 13 16:40:11 citusc17 rpc.lockd: Found CLIENT* in cache > Nov 13 16:40:31 citusc17 rpc.lockd: process ID: 10865 > Nov 13 16:40:31 citusc17 rpc.lockd: fh_len 24, fh \01\00\00\02\00\08\00\07\02\00\00\00\40\a0\0e\00\73\09\c6\11\2a\a0\0e\00 > Nov 13 16:40:31 citusc17 rpc.lockd: start 0; len 0; pid 1; type 1; whence 0 > Nov 13 16:40:31 citusc17 rpc.lockd: wait was not set > Nov 13 16:40:31 citusc17 rpc.lockd: lock request: V4: read to 128.125.38.123 > Nov 13 16:40:31 citusc17 rpc.lockd: Found CLIENT* in cache > > (this repeats every 20 seconds) Neither the tcpdump nor the lockd debug output show any response from the server... can you look into this? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021114013320.GA50692>