1 (edited by gilles.quenot 2019-04-04 18:35:35)

Topic: SoGo 4.0.7 performances issues, high load

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail 0.9.9
- Debian9
- MySQL
- Nginx
====

Hi,

since upgrade from SoGo 3.* to 4.*, I have some performances issues.

I had to reboot my unreachable server last minutes ago, and I fight with my system to keep it up (high load, web UI not responsive, bad gateway error).

I was not encountering this issues with SoGo 3.

Can I go back to 3 or is there a workaround ? I followed the doc here to upgrade.

cpu 2 cores Intel(R) Atom(TM) CPU D425   @ 1.80GHz
2GB RAM
PREFORK=25 in /etc/default/sogo

Is there a doc to downgrade ?

Regards

Edit: was totally out of memory (syslog) :

Apr  4 12:05:31 mail1 cron[560]: /usr/sbin/postdrop: error while loading shared libraries: libdl.so.2: failed to map segment from share
d object
Apr  4 12:05:36 mail1 postfix/master[2139]: warning: unix_trigger_event: read timeout for service public/pickup
Apr  4 12:05:47 mail1 cron[560]: sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 127
Apr  4 12:05:49 mail1 CRON[18584]: (CRON) error (can't fork)
Apr  4 12:06:07 mail1 cron[560]: sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 127
Apr  4 12:06:09 mail1 CRON[18596]: (CRON) error (can't fork)
Apr  4 12:06:13 mail1 cron[560]: sendmail: fatal: root(0): unable to execute /usr/sbin/postdrop -r: Success
Apr  4 12:06:19 mail1 CRON[18595]: (CRON) error (can't fork)
Apr  4 12:06:44 mail1 cron[560]: sendmail: fatal: root(0): unable to execute /usr/sbin/postdrop -r: Success
Apr  4 12:06:49 mail1 kernel: [161731.335338] systemd-journal: page allocation stalls for 19824ms, order:0, mode:0x24201ca(GFP_HIGHUSER
_MOVABLE|__GFP_COLD)
Apr  4 12:06:54 mail1 kernel: [161731.338943] CPU: 0 PID: 421 Comm: systemd-journal Not tainted 4.9.0-8-amd64 #1 Debian 4.9.144-3.1
Apr  4 12:06:54 mail1 kernel: [161731.342208] Hardware name:  /D425KT, BIOS MWPNT10N.86A.0083.2011.0524.1600 05/24/2011
Apr  4 12:06:54 mail1 kernel: [161731.343919]  0000000000000000 ffffffffaa534524 ffffffffaac01e18 ffffadc0c06c7b78
Apr  4 12:06:54 mail1 kernel: [161731.343919]  ffffffffaa38bfaa 024201ca00000000 ffffffffaac01e18 ffffadc0c06c7b18
Apr  4 12:06:54 mail1 kernel: [161731.343919]  0000000000000010 ffffadc0c06c7b88 ffffadc0c06c7b38 dee47ced366d298c
Apr  4 12:06:54 mail1 kernel: [161731.343919] Call Trace:
Apr  4 12:06:54 mail1 kernel: [161731.343919]  [<ffffffffaa534524>] ? dump_stack+0x5c/0x78
Apr  4 12:06:54 mail1 kernel: [161731.343919]  [<ffffffffaa38bfaa>] ? warn_alloc+0x13a/0x160
Apr  4 12:06:54 mail1 kernel: [161731.343919]  [<ffffffffaa38c99d>] ? __alloc_pages_slowpath+0x95d/0xbb0
Apr  4 12:06:54 mail1 kernel: [161731.343919]  [<ffffffffaa3de751>] ? alloc_pages_current+0x91/0x140
Apr  4 12:06:54 mail1 kernel: [161731.373180]  [<ffffffffaa38cdf1>] ? __alloc_pages_nodemask+0x201/0x260
Apr  4 12:06:54 mail1 kernel: [161731.373180]  [<ffffffffaa3de751>] ? alloc_pages_current+0x91/0x140
Apr  4 12:06:54 mail1 kernel: [161731.373180]  [<ffffffffaa385966>] ? filemap_fault+0x326/0x5d0
Apr  4 12:06:54 mail1 kernel: [161731.383454]  [<ffffffffc0c39a41>] ? ext4_filemap_fault+0x31/0x50 [ext4]
Apr  4 12:06:54 mail1 kernel: [161731.383454]  [<ffffffffaa3b6557>] ? __do_fault+0x87/0x170
Apr  4 12:06:54 mail1 kernel: [161731.383454]  [<ffffffffaa3bafa7>] ? handle_mm_fault+0xeb7/0x1310
Apr  4 12:06:54 mail1 kernel: [161731.383454]  [<ffffffffaa40aacd>] ? new_sync_read+0xdd/0x130
Apr  4 12:06:54 mail1 kernel: [161731.383454]  [<ffffffffaa2622f5>] ? __do_page_fault+0x255/0x4f0
Apr  4 12:06:54 mail1 kernel: [161731.401197]  [<ffffffffaa81a618>] ? page_fault+0x28/0x30

2

Re: SoGo 4.0.7 performances issues, high load

Hi,

can I keep new database schema with Sogo 3 ?

Regards, GQ

3

Re: SoGo 4.0.7 performances issues, high load

What I have done :

systemctl stop sogo
systemctl status sogo
mkdir sogo4-backup
mv sogo-backup sogo3-backup
cp /etc/sogo/* sogo4-backup/
cp /etc/default/sogo sogo4-backup/
cp sogo3-backup/default/sogo /etc/default/sogo 
diff -aqr sogo3-backup/sogo/ /etc/sogo/
cp sogo3-backup/sogo/sogo.conf /etc/sogo/sogo.conf
vi /etc/apt/sources.list # back to v3
apt remove sogo.*
apt update 
apt upgrade
apt install sogo sogo-activesync
systemctl status sogo
htop # very good now 

4

Re: SoGo 4.0.7 performances issues, high load

But nothings works anymore after reboot :

Apr 06 09:44:02 sogod [1973]: [ERROR] <0x55d0cc111260[SOGoMailAccount]:0> Could not connect IMAP4Apr 06 09:44:02 sogod [1981]: <0x55d0cc228600[SOGoMailAccount]:0> renewing imap4 password

Maybe an issue with MySQL schema ?

5

Re: SoGo 4.0.7 performances issues, high load

The problem is lack of memory, not SOGo v3 or v4 issue.
SOGo itself requires a lot memory, you have 25 prefork child processes for ActiveSync, try to decrease the number, or increase the memory, then issue will be solved.

For ActiveSync connection, SOGo requires at least 1 long-run http connection, 2 SQL connections, 20-50MB memory.

----

Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee

6

Re: SoGo 4.0.7 performances issues, high load

No, PREFORK is 10 like before upgrade, and htop report a normal usage of RAM, and low load average.

The problem is not there

7 (edited by gilles.quenot 2019-04-08 04:09:58)

Re: SoGo 4.0.7 performances issues, high load

Reinstalled iRedMail.

@admin: Iredmail reinstall script for debian/mysql/nginx configuration :

https://github.com/sputnick-dev/iRedMai … stall.bash

Maybe can be added to doc ? If you want improvements, please ask.

System footprint, quite good now \o/ (sogo 4) :

https://i.imgur.com/uaIGEzi.png