Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-02-03 Thread Greg Kunyavsky
On 17-01-26 07:26 PM, Ludovic Marcotte (lmarco...@inverse.ca) wrote: On 2017-01-26 6:33 PM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote: I followed the FAQ to install -dbg packages and run GDB. I only had to change -WOUseWatchDog to YES, otherwise only 1 worker runs instead of 600.

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-26 Thread Ludovic Marcotte
On 2017-01-26 6:33 PM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote: I followed the FAQ to install -dbg packages and run GDB. I only had to change -WOUseWatchDog to YES, otherwise only 1 worker runs instead of 600. Unfortunately the stack trace does not look very useful. Any suggestions?

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-26 Thread Greg Kunyavsky
On 17-01-24 07:14 AM, Ludovic Marcotte (lmarco...@inverse.ca) wrote: On 2017-01-24 1:42 AM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote: I am no closer to finding the issue, but I am getting this message pretty consistently *** stack smashing detected ***: /usr/sbin/sogod terminated But

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-24 Thread Ludovic Marcotte
On 2017-01-24 1:42 AM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote: I am no closer to finding the issue, but I am getting this message pretty consistently *** stack smashing detected ***: /usr/sbin/sogod terminated But no core file. Try starting SOGo from gdb - so don't reduce the number

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-24 Thread Greg Kunyavsky
I am no closer to finding the issue, but I am getting this message pretty consistently *** stack smashing detected ***: /usr/sbin/sogod terminated But no core file. How do I get a core dump? I tried setting ulimit and /proc/sys/kernel/core_pattern root@mail01:~#ulimit -c unlimited

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-09 Thread Greg Kunyavsky
On 17-01-09 04:13 PM, Ludovic Marcotte (lmarco...@inverse.ca) wrote: Check of your "sogo" user isn't running out of file descriptors for the master sogod process. Do a "su - sogo" and run "ulimit -n". I did have errors earlier that hinted at running out of file descriptors, but I thought I

Re: [SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-09 Thread Ludovic Marcotte
On 2017-01-09 3:45 PM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote: We are hoping to support several thousand push email users using sogo. I am trying to push the worker count higher. Currently I am not testing any clients yet, just trying to get sogo to start with a large number of worker

[SOGo] At WOWorkersCount 600 keep consuming CPU and RAM with no clients connected.

2017-01-09 Thread Greg Kunyavsky
Hello, We are hoping to support several thousand push email users using sogo. I am trying to push the worker count higher. Currently I am not testing any clients yet, just trying to get sogo to start with a large number of worker processes and sit idle. At 400 processes, they take 27MB