Hello,
yesterday on one of our SOGo servers sogod was killed by Linux’ oom-killer
– kernel log:
Out of memory: Killed process 2184654 (sogod) …
Prior this we saw a massive increase in memory usage within 30 seconds. In
sogo.log we see:
2025-07-29 15:12:27.621 sogod[1672:2184654] WARNING(-[NGBufferedStream
writeBytes:count:]): got passed in length 190MB (199833590 bytes,
errcode=2147483647) ...
…
Jul 29 15:12:38 sogod [1672]: <0x0x564af06caa30[WOWatchDogChild]> child
2184654 exited
Jul 29 15:12:38 sogod [1672]: <0x0x564af06caa30[WOWatchDogChild]>
(terminated due to signal 9)
After this all sogo processes where terminated by further oom-killer
actions. Not good at all.
sogod runs with -WOWorkersCount 50, config sets SxVMemLimit = 512;
The server’s memory is 16 GBytes. This is usually sufficient, but might be
not: 50 * 512 M > 16 G
What does the WARNING (-[NGBufferedStream writeBytes:count:]) … log mean? We
saw some of them.
Has anybody written a systemd unit file for sogo … with Restart=on-failure?
Any further hints welcome!
Thanks,
Frank
--
Frank Richter, Chemnitz University of Technology, Germany
