On 08/14/15 08:11 -0700, Shaheen Bakhtiar wrote: >> On Aug 14, 2015, at 8:03 AM, Dan White <dwhite@xxxxxxx> wrote: >> On 08/14/15 07:46 -0700, Shaheen Bakhtiar wrote: >>> Ever since the rebuild we are experience an ever growing number of imapd >>> processes, when we first boot the server we have ~200 using 2.4G of >>> memory. In about 3 to 4 days we have ~1500 imapd processes taking up all >>> available physical memory and all all available swap memory (an additional >>> 4G). >>> >>> and our logs are filled with messages like: >>> Aug 14 06:26:01 postoffice kernel: Out of memory: Kill process 15427 (imapd) score 1 or sacrifice child >>> Aug 14 06:26:01 postoffice kernel: Killed process 15427 (imapd) total-vm:179648kB, anon-rss:7756kB, file-rss:672kB >> >> How many processes spawn is configurable within /etc/cyrus.conf. How do you >> have your imap entries configured? > >[shawn@postoffice ~]$ more /etc/cyrus.conf > imap cmd="imapd" listen="imap" prefork=5 > imaps cmd="imapd -s" listen="imaps" prefork=1 You can limit the damage with a maxchild option (cyrus.conf(5)). -- Dan White ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
