17 Apr
2008
17 Apr
'08
7:11 p.m.
On Apr 17, 2008, at 6:56 PM, richs@whidbey.net wrote:
We recently began seeing server crashes in our cluster related to
"pop3-login", which is causing "oom-killer" to be invoked. The
server only recovers after a reboot.
So oom-killer doesn't solve the issue? Then it's likely it has nothing
to do with pop3-login, OOM killer just selects a bad target to kill
(and Dovecot happily restarts a new pop3-login process) while the real
memory-eating process stays alive. Can you check with ps what
process(es) are eating all the memory?