Hello, When one of my users tries to log in, he gets 502 Proxy error. In the background, the sogod process is killed by OOM killer:
> Memory cgroup out of memory: Kill process 11811 (sogod) score 962 or > sacrifice child > Killed process 11811 (sogod) total-vm:1385268kB, anon-rss:1006060kB, > file-rss:0kB When I stop Dovecot, the user can login (but obviously can't use e-mail). After some debugging I realized that there was more than 30 000 messages in his inbox. I understand that this is huge amount of e-mails and not a typical use case, but I hope that SOGo could behave stable even in such cases. When I added some swap, sogod ate about 4 GB of memory and then run out of it. However the filesystem is not slow – directory listing time: > # time ls -l | wc -l > 32574 > > real 0m0.362s > user 0m0.170s > sys 0m0.195s and total size of given e-mails is not too much: > # du . > 169M So why is not 4 GB of RAM enough to show list of messages? Of course, there are some metadata and MIME messages are parsed, not only raw data… Maybe there could be some configurable limit of messages above which SOGo will refuse listing particular folder but will not eat all memory. BTW: My SxVMemLimit has default value (384). I tried to increase this value but it didn't help. Regards, Franta P.S. my solution was deleting the messages (most of them was useless notifications), so this request is not urgent – but maybe there is some bug or some place for improvement. P.P.S. despite this issue, thanks for SOGo, the great groupware software! -- [email protected] https://inverse.ca/sogo/lists
