On 2014-06-02, 9:33 AM, VILLEMUR Jacques wrote:
Hello,
Our service sogo crashes several times a day (process 100% cpu, pid
xxxx has-been hanging in the same request for ...). If I stop the
process and restarts sogo works fine (so I concluded that it is not a
resource problem - ldap, imap, case: no error on these servers - ).
Here is our configuration:
VM: sogo server 2.2.3-1 centos 6.5 (8cpu 8GB)
CAS, LDAP, IMAP/SIEVE postgres different servers
Nrb potential USERS: 1500
Sogo configuration:
/etc/sysconfig = prefork = 12
/etc/sogo/sogo.conf
WOListenQueueSize = 64;
SxVMemLimit = 600;
...
Do you have any idea?
I watched with gdp -p <processs to 100%>: I have nothing particular to
(I'm not a specialist gdb)
Have a look at
http://www.sogo.nu/fr/nc/support/faq/article/how-do-i-debug-sogo.html
When you see "pid xxxx has-been hanging in the same request for ...)",
attach specifically to that PID and produce a backtrace.
Thanks,
--
Ludovic Marcotte
lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence
(http://packetfence.org)
--
users@sogo.nu
https://inverse.ca/sogo/lists
