On Sat, Mar 15, 2003 at 01:33:11AM -0600, Dan Nelson wrote:
>
> Oops. You appended a decoded dump again. I should have told you how
> to generate a raw tcpdump log. Add "-s 1500 -w file.pcap" to the
> tcpdump commandline. You won't get any output to the screen, but the
> raw packet contents will get written to the file. You can replay it
> with tcpdump -r, or load it into ethereal and view the packets in the
> GUI.
Sorry - I was trying to be too helpful. I actually did capture the raw
dump but appended the decoded output. This time, I've attached a
real raw dump.
>
> Runs fine on my Solaris 2.6 and 2.7 machines, so it's not a
> Solaris->FreeBSD specific problem.
I was already pretty sure that's true - I actually did have it working
for some number of days. I just don't know what broke it.
>
> Ok, it definitely dies trying to lock the file. Check to make sure
> that rpc.lockd is still running on the FreeBSD server. I have seen it
> coredump on a couple of my 4.5 servers and the result was what you're
> seeing here (lock attempts hang).
>
rpc.lockd and rpc.statd still running on Freebsd, lockd and statd
still running on Solaris.
I hope the tcpdump gives you a clue what might be going wrong...
Thanks.
Steve
--
Steve Sizemore <[EMAIL PROTECTED]>, (510) 642-8570
Unix System Manager
Dept. of Mathematics and College of Letters and Science
University of California, Berkeley
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
