For posterity and the list archives: We believe we identified our problem. A previous administrator made source changes to our packages to remove the requirement of the frontends' SSL communication with the backends, since these machines are utterly private inside our network and he wanted to 1) make debugging easier, and 2) reduce performance and administration overhead. John Masterson wrote: > We just upgraded to 2.2.13-10+etch2 and now our 64bit front end machines > cannot connect to our back end servers, e.g., > > > Sep 13 11:55:49 mfe5 cyrus/mc2pop3[6764]: > connect(mbe2.msomt.modwest.com) failed: Invalid argument > Sep 13 11:55:49 mfe5 cyrus/mc2pop3[6764]: couldn't authenticate to > backend server > > also: > > Sep 13 15:15:39 mfe5 cyrus/mupdate[1327]: Thread timed out waiting for > listener_lock > > > > A 32-bit front end machine is working fine. We don't think there are any > other differences between these installations. cyrus.conf, mupdate.conf, > and imap.conf are identical except for the obvious, listen addresses, > hostnames. > > > Any ideas or experience with this? > > -- > John Masterson > http://modwest.com > > > > > > > > ---- > Cyrus Home Page: http://cyrusimap.web.cmu.edu/ > Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki > List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html > > > ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
