Harald Barth wrote: > You probably mean stuff like this: > > Wed Oct 5 17:31:21 2005 FindClient: client 8320a78(6d5cb8f8) already had > conn a7071568 (host 3fdded82), stolen by client 8320a78(6d5cb8f8)
> I have only ONE such log line and not for the time frame in question. > 3fdded82 is my laptop 130.237.221.63 when at work. But I have no such > message for any of its other IPs which would be *eded82 (130.237.237.*) > - my laptop when at home. This log message is not a symptom of the bug that was fixed related to UUID collision. This problem you are seeing may or may not be related and it may or may not be an actual bug. > I moved my H.haba.mail volume to another server which allows me to gdb > and stop the fileserver without been lynched but of course the > problems dissapeared when I did that. Probably I need to use up some > kind of resource in the fileserver/rx first. I don't know how without > letting loose real users. I know I have many connections from many > clients. But a lot of free threads and no CPU or I/O load to speek of. > Feel free to run rxdebug against houting.pdc.kth.se if you think you > see something that I don't. Any tips how to collect statistics? > > Harald. I doubt moving your volume is going to help track down the problem. You are not going to have lots of other users connecting to the new server. I don't think we need to be able to stop the service. However, it would be useful to see what the server is doing in Ethereal. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
