Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-18 Thread nuitari-dovecot
That fixed it for me as well. You can get the patch from gitweb at (formatting is a bit nicer for patching): http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=711a49a07f84f914aac26a52143f6e7526571143 It is not fixed in 2.6.27.9, but will be fixed in 2.6.27.10 according

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-18 Thread Patrick McLean
Steffen Weber wrote: > Just saw this thread on > This fix seems to work for me: > http://lkml.indiana.edu/hypermail/linux/kernel/0812.1/00998.html That fixed it for me as well. You can get the patch from gitweb at (formatting is a bit nicer for patching): http://git.kernel.org/?p=linux/kernel/git

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-15 Thread nuitari-dovecot
On Mon, 15 Dec 2008, Steffen Weber wrote: Just saw this thread on http://dovecot.org/list/dovecot/2008-December/035707.html and I hope that this email gets through (I'm not subscribed). The described behaviour seems to be a bug in Linux 2.6.27.8: http://lkml.indiana.edu/hypermail/linux/kerne

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-15 Thread Steffen Weber
Just saw this thread on http://dovecot.org/list/dovecot/2008-December/035707.html and I hope that this email gets through (I'm not subscribed). The described behaviour seems to be a bug in Linux 2.6.27.8: http://lkml.indiana.edu/hypermail/linux/kernel/0812.1/6.html This fix seems to work

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-13 Thread nuitari-dovecot
Wow. Yeah, *some*thing's changed recently to cause this. If I had to guess, I'd say it's a recent Thunderbird upgrade that's triggering it, as it's been 2-3 weeks since my last dovecot upgrade. Some other interesting data points: * This problem seems to happen when I use Thunderbird (both

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-13 Thread Darren Pilgrim
David Rosenstrauch wrote: On Sat, December 13, 2008 12:28 am, Timo Sirainen wrote: On Dec 13, 2008, at 3:40 AM, David Rosenstrauch wrote: In recent days, dovecot's "imap" processes keep getting stuck. Each time I check my server (running dovecot 1.1.7) there's a bunch of "imap" processes (som

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-13 Thread David Rosenstrauch
David Rosenstrauch wrote: Wow. Yeah, *some*thing's changed recently to cause this. If I had to guess, I'd say it's a recent Thunderbird upgrade that's triggering it, as it's been 2-3 weeks since my last dovecot upgrade. Some other interesting data points: * This problem seems to happen when

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-13 Thread David Rosenstrauch
On Sat, December 13, 2008 9:14 am, David Rosenstrauch wrote: > Wow. Yeah, *some*thing's changed recently to cause this. If I had to > guess, I'd say it's a recent Thunderbird upgrade that's triggering it, as > it's been 2-3 weeks since my last dovecot upgrade. Or perhaps it's a recent kernel up

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-13 Thread David Rosenstrauch
On Sat, December 13, 2008 12:28 am, Timo Sirainen wrote: > On Dec 13, 2008, at 3:40 AM, David Rosenstrauch wrote: > >> In recent days, dovecot's "imap" processes keep getting stuck. Each >> time I check my server (running dovecot 1.1.7) there's a bunch of >> "imap" processes (sometimes 2 of them,

Re: [Dovecot] Dovecot imap processes pinning CPU

2008-12-12 Thread Timo Sirainen
On Dec 13, 2008, at 3:40 AM, David Rosenstrauch wrote: In recent days, dovecot's "imap" processes keep getting stuck. Each time I check my server (running dovecot 1.1.7) there's a bunch of "imap" processes (sometimes 2 of them, sometimes 4, sometimes 6) that are using all of the box's CPU.

[Dovecot] Dovecot imap processes pinning CPU

2008-12-12 Thread David Rosenstrauch
In recent days, dovecot's "imap" processes keep getting stuck. Each time I check my server (running dovecot 1.1.7) there's a bunch of "imap" processes (sometimes 2 of them, sometimes 4, sometimes 6) that are using all of the box's CPU. And worse, there's no way to kill the processes either (n