Hi, I'm running dovecot on an Ubuntu server (1:1.0.5-1ubuntu2). Dovecot provides pop3, imap, and sasl to postfix. The setup works quite nicely, however I do have one error that shows up repeatedly in my dovecot.log. <snip> dovecot: 2007-12-12 09:29:06 Error: child 32765 (login) killed with signal 9 dovecot: 2007-12-12 09:29:06 Error: child 18039 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 26088 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 5271 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 5273 (login) killed with signal 9 <snip> I'm not aware that this is actually causing problems, but since it shows up several hundred times a day on a couple-user setup, I'm rather curious about what's causing it. Thanks, Matt
Anyone? Bueller? On Dec 12, 2007 9:19 PM, Matt LaPlante <cyberdog3k at gmail.com> wrote:> Hi, > I'm running dovecot on an Ubuntu server (1:1.0.5-1ubuntu2). Dovecot > provides pop3, imap, and sasl to postfix. The setup works quite > nicely, however I do have one error that shows up repeatedly in my > dovecot.log. > > <snip> > dovecot: 2007-12-12 09:29:06 Error: child 32765 (login) killed with signal 9 > dovecot: 2007-12-12 09:29:06 Error: child 18039 (login) killed with signal 9 > dovecot: 2007-12-12 10:05:07 Error: child 26088 (login) killed with signal 9 > dovecot: 2007-12-12 10:05:07 Error: child 5271 (login) killed with signal 9 > dovecot: 2007-12-12 10:05:07 Error: child 5273 (login) killed with signal 9 > <snip> > > I'm not aware that this is actually causing problems, but since it > shows up several hundred times a day on a couple-user setup, I'm > rather curious about what's causing it. > > Thanks, > Matt >
On 13.12.2007, at 4.19, Matt LaPlante wrote:> dovecot: 2007-12-12 09:29:06 Error: child 32765 (login) killed with > signal 9Well, your message inspired me to waste some time and money on creating a new wiki: http://www.unixcoding.org/ and add a page there: http://www.unixcoding.org/Signals: SIGKILL Number: 9 Killed by kernel, for example Linux's Out of Memory killer. dmesg may show the reason. Does setting login_process_size=64 fix this? If so, I'll update that text to mention setrlimit() address space limit. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071216/eb40523b/attachment-0002.bin>
On Dec 16, 2007 3:15 PM, Timo Sirainen <tss at iki.fi> wrote:> On 13.12.2007, at 4.19, Matt LaPlante wrote: > > > dovecot: 2007-12-12 09:29:06 Error: child 32765 (login) killed with > > signal 9 > > Well, your message inspired me to waste some time and money on > creating a new wiki: http://www.unixcoding.org/ and add a page there: > http://www.unixcoding.org/Signals: > SIGKILL > > Number: 9 > > Killed by kernel, for example Linux's Out of Memory killer. dmesg may > show the reason.I'm familiar with sigkill. :) The mystery to me is who is sending the signals... There is no evidence of anything in dmesg or syslog. free reports consistent amounts of space available, and none of my other daemons seem to be subject to any ill effects. Client connection rates are very minimal and consistent. To answer Bill, there are no cron jobs on the system doing any sort of babysitting that would be killing processes. Being openvz, I suppose there is room for shenanigans to be occurring in the background, but it doesn't really explain why only dovecot seems to be affected. (Unless it's a matter of perception, and only dovecot is logging such things).> > Does setting login_process_size=64 fix this? If so, I'll update that > text to mention setrlimit() address space limit.This is currently 32 (according to dovecot.conf). Wouldn't raising it to 64 exacerbate memory problems if they do indeed exist?> >