Hi, i was having the exact same issues with sogo, workers maxing out one or more cores. In our case raising the max. numbers of concurrent IMAP-logins for dovecot fixed it. Looks like sogo died trying to login, as soon as dovecot would deny any new sessions. Go figure.... __ Regards, Jochen Rosenbauer Am 14.11.2012 14:56 schrieb "Mathilde Rousseau" < mathilde.rouss...@icsn.cnrs-gif.fr>:
> Hello > I have a trouble since this morning and i don't know why. I didn't do any > upgrade or any change on the configuration file. My server is running on a > debian squeeze 64 bits. I am running sogo2.0.2. > If i try to connect with the WEB UI it is really very very slow and when i > look in the https-error.log i have this error : > > (104)Connection reset by peer: proxy: error reading status line from > remote server 127.0.0.1:20000 > [Wed Nov 14 14:53:20 2012] [error] [client 157.136.38.164] proxy: Error > reading from remote server returned by /SOGo/dav/mathilde/Calendar/** > personal/ > > I didin't find any thing wrong in the sogo log files. > If i run top i can see that sogod use 100 % of the CPU. > If someone could help me, i will really appreciate. > Kind regards > Mathilde > > -- > Mathilde Rousseau tel: 01 69 82 45 84/ 06 10 27 96 32 > Responsable du Service Informatique Commun, > ICSN UPR2301, Bâtiment 27 > CNRS, 1 Av de la terrasse mail: mathilde.rouss...@icsn.cnrs-* > *gif.fr <mathilde.rouss...@icsn.cnrs-gif.fr> > 91198 Gif sur Yvette cedex > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists > -- users@sogo.nu https://inverse.ca/sogo/lists
