Lock problem with mupdate

Dave McMurtrie dave64 at andrew.cmu.edu
Tue Apr 17 05:43:41 EDT 2012

strace the server and find out what it's doing.  Look at the logs on the server.  Run netstat to confirm both sides still have an established connection and that iptables isn't silently dropping packets, etc.

On Apr 17, 2012, at 5:10 AM, Frank Elsner <Frank.Elsner at TU-Berlin.DE> wrote:

> On Tue, 17 Apr 2012 04:41:57 -0400 Dave McMurtrie wrote:
>> lsof so you can find out what file descriptor 9 is that read() is blocking on.  If it's the socket to your mupdate server, figure out why it isn't responding.
> Thanks. Indeed it is the connection to the mupdate server:
> mupdate 7395 cyrus    9u  IPv4            3273817      0t0     TCP eg-mailfrontend-febe.intern.elgouna.tu-berlin.de:40362-> (ESTABLISHED)
> So we have to investigate why we can ping in both directions, why the 
> frontend can autheticate on the mupdate server and why the answer doesn't get 
> through.
> Thanks so far, 
> Frank Elsner

More information about the Info-cyrus mailing list