Hi, We have managed to solve it, it's not a locking of threading issue. All we had to do is recompile cyrus sasl with /dev/urandom instead of /dev/random.
This caused me a lot of trouble the last week. So I hope if some people face this problem they know where to search. Don't say a word! We feel pretty fucked now. Regards, Matthijs Mohlmann Matthijs Mohlmann wrote: > Hi, > > I have here a murder cluster with the following setup: > > Cyrus Master: > CPU: Pentium 3 1Ghz > Memory: 1GB > Distro: Debian GNU/Linux > > Cyrus Backend / Frontend (backend and frontend are running a separate > master process): > CPU: Pentium 3 1Ghz > Memory: 2GB > Distro: Debian GNU/Linux > > Cyrus Backend / Frontend (backend and frontend are running a separate > master process): > CPU: Dual Xeon 2.4Ghz > Memory: 2GB > Distro: Debian GNU/Linux > > All are running the cyrus packages from http://debian.speedblue.org/. > > On the single processor box everything goes ok. On the dual processor > box I have a lot of trouble. When enabling the imap / pop3 proxies on > the frontend then after a while the complete murder setup is hanging. > After restarting the master everything is ok again. This only happens > when I enable the imap / pop3 proxies on the dual processor box. With > the lmtp frontend I don't have any problems, but that one is directly > connecting to the master server. > > So it seems to me there is something going wrong with the mupdate > communication to the master. > > My question: are there any patches or configuration items that are > addressing this issue ? > > If you need more information about the configs or need to have some gdb > traces please contact me. > > Regards, > > Matthijs Mohlmann ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
