Hi,
I tried different numbers of sogod workers. Nothing worked. Since this
happens in our production server i can't investigate the problem if it
happens through the day.
Fortunately is right now happening an everyone already left the office.
This means 2 things:
1. There is not really any
I need to correct myself. The backtraces are only identical up to line 16.
It seems that this is not code from SOGo. So it may be a bug in gnustep
or libc.
Since this server is still running debian lenny, it may be fixed in
squeeze.
Upgrade is planned anyway. I'll write again if the problem
Hi,
In the last weeks we are facing a problem with our SOGo server.
From time to time (sometimes twice a day) the parent process consumes
full cpu.
We tried several things and are out of ideas right now. It looks like
the child processes are somehow occupied in a request but do not need
any
On 18/07/11 07:13, Raffael Bachmann wrote:
From time to time (sometimes twice a day) the parent process consumes
full cpu.
That happens when all sogod workers are doing some work - the parent
process will spin very quickly trying to find an available worker.
Increase the number of sogod
Thanks for the fast answer.
How many workers would you suggest? I tried it once with 6 and 10 but
because of the memory consumption (swapping) the server became even less
responsive.
Right now we are using 4 workers.
Couldn't it be that this aggressive waiting strategy could even prevent
On 07/18/2011 03:49 PM, André Schild wrote:
Am 18.07.2011 15:38, schrieb Raffael Bachmann:
Thanks for the fast answer.
How many workers would you suggest?
I think this depends on the number of clients which are actively
accessing your sogo server ;)
There are about 30 users with
On 18/07/11 15:00, Raffael Bachmann wrote:
On 07/18/2011 03:49 PM, André Schild wrote:
Am 18.07.2011 15:38, schrieb Raffael Bachmann:
Thanks for the fast answer.
How many workers would you suggest?
I think this depends on the number of clients which are actively
accessing your sogo
