1

Topic: SOGo tuning

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.3
- Linux/BSD distribution name and version: CentOS 7.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:
====

Hi all,
being new here, first an organisational question: how can one search in this forum??

Now to my issue:
I had a (more or less) running environment on CentOS 6 with PGSQL and OpenLDAP with a lot of drawbacks due to my lack of knowledge of Linux based environments. Performance was the only thing I never had to think about, it was just working fine.

Because of the abovementioned lack of knowledge I moved on to a new server, comparable hardware, using iRedMail, SOGo, Apache and MySQL. Now all (or most ;-)  ) of the issues I had are gone but I run into huge performance issues mainly visible in SOGo webUI but there all the time, also using EAS. IMAP via Thunderbird seems to be fine though. Restart of SOGod Service brings temporary relief but after a few minutes all gets very sluggish again. I got a lot of good advice regarding tweaking the parameters in sogo.conf and httpd/sogo.conf but I want to look outside and possibly find ideas about tweaking Mysql and the System in relation to SOGo. Anyone any ideas?

I run a rather small Environment with max.100 mailboxes (currently only 15), but all with at least 1 or 2 EAS Clients (Outlook 2013+, IOS and Android) syncing ...

many thanks in advance

Andy

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: SOGo tuning

It's hard to help without any error message.

*) A basic tuning is increasing the preforked sogo processes in /etc/sysconfig/sogo to handle more clients.
*) Another tuning is mentioned in SOGo installation guide:
http://sogo.nu/support/index.html#/documentation

3

Re: SOGo tuning

Hi,
I have with lots of help ruled out most errors already, what remains are plenty of these Errors in /etc/sogo/sogo.log:

Feb 12 17:59:17 sogod [10863]: [ERROR] <0x0x7f23279c12e0[WOHttpTransaction]> client disconnected during delivery of response for <WORequest[0x0x7f2327782e60]: method=POST uri=/SOGo/Microsoft-Server-ActiveSync?Cmd=Ping&User=user@domain.tld&DeviceId=android123456789012&DeviceType=Android app=SOGo rqKey=Microsoft-Server-ActiveSync rqPath=(null)> (len=20): the socket was shutdown

occurring for all actively synced EAS devices, in total like 10 per Minute

When restarting sogod, after 15 to 20 minutes webui and overall access gets very slow.

current relevant settings are
PREFORK=72 (estimated 60 EAS devices)
SOGoMaximumPingInterval = 354;
SOGoMaximumSyncInterval = 354;
SOGoInternalSyncInterval = 30;
WOWatchDogRequestTimeout = 6;
SOGoMaximumSyncResponseSize = 512;
SOGoMaximumSyncWindowSize = 256;
SxVMemLimit = 512;

ProxyPass /Microsoft-Server-ActiveSync \
    http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \
    retry=60 connectiontimeout=5 timeout=360

any help is much appreciated!

ZhangHuangbin wrote:

It's hard to help without any error message.

*) A basic tuning is increasing the preforked sogo processes in /etc/sysconfig/sogo to handle more clients.
*) Another tuning is mentioned in SOGo installation guide:
http://sogo.nu/support/index.html#/documentation

4

Re: SOGo tuning

Did you try this?

SOGoMaximumPingInterval = 3540;
SOGoMaximumSyncInterval = 3540;
SOGoInternalSyncInterval = 30;

This is mentioned in SOGo installation guide, it works for me. But i don't have as many clients as you.

If it still raises error, it's better to post in SOGo mailing list to get support from SOGo developers.
http://sogo.nu/support/index.html#/community

5 (edited by ablaha 2016-02-17 23:29:01)

Re: SOGo tuning

ZhangHuangbin wrote:

Did you try this?

SOGoMaximumPingInterval = 3540;
SOGoMaximumSyncInterval = 3540;
SOGoInternalSyncInterval = 30;

I actually did try all this, the effect is minimal but causes other side effects like synchronization stopping to work for Outlook EAS Clients so I went back to

PREFORK=100
SOGoMaximumPingInterval = 354;
SOGoMaximumSyncInterval = 354;
SOGoInternalSyncInterval = 30;
WOWatchDogRequestTimeout = 6;

as this caused the least problems. Still, the performance is dull, so I was hoping to find some tweaking outside SOGo, like the relation to MySQL, e.g. how can I find out whether the database is coping with the settings definend in SOGo?

6

Re: SOGo tuning

ablaha wrote:

how can I find out whether the database is coping with the settings definend in SOGo?

I'm afraid that i don't quite understand this question. What do you mean "database is coping with the settings defined in SOGo"?

7

Re: SOGo tuning

ZhangHuangbin wrote:
ablaha wrote:

how can I find out whether the database is coping with the settings definend in SOGo?

I'm afraid that i don't quite understand this question. What do you mean "database is coping with the settings defined in SOGo"?

Something like the relation of the ProxyPass Statement (timeout 360s) in httpd/sogo.conf compared to WOWatchDogRequestTimeout = 6 (minutes) in sogo.conf;

It is just a thought, maybe MySQL needs some tuning too or I am running into some preconfigured limitations there, it is just not mentioned anywhere.   
As I am no Pro and just starting to understand how things work in Linux I am desparately looking for some ideas.

8

Re: SOGo tuning

By the way, for CentOS/RHEL, prefork must be defined in /etc/sysconfig/sogo. (and /etc/default/sogo for Debian/Ubuntu)