I have this EXACT same problem after upgrading to SuSE 11.1, which uses this
exact kernel version!!
After reading this, I was excited to think that if I killed the nfsserver
daemon (which I had running for no good reason), that it would sort my
problem
Sure enough, my computer - which up to
On Feb 14, 2009, at 9:57 AM, agent59624285 wrote:
I have this EXACT same problem after upgrading to SuSE 11.1, which
uses this
exact kernel version!!
After reading this, I was excited to think that if I killed the
nfsserver
daemon (which I had running for no good reason), that it would
On Sun, 2009-02-15 at 12:10 -0700, Gene Steinberg wrote:
This is sounding similar to the problem I have with my setup:
1. High CPU usage.
2. Can't kill IMAP.
kill -9 doesn't work for imap processes? You didn't mention this before.
I'm using CentOS 5.2 64-bit version with the latest
On Feb 15, 2009, at 12:43 PM, Timo Sirainen wrote:
On Sun, 2009-02-15 at 12:10 -0700, Gene Steinberg wrote:
This is sounding similar to the problem I have with my setup:
1. High CPU usage.
2. Can't kill IMAP.
kill -9 doesn't work for imap processes? You didn't mention this
before.
Timo Sirainen wrote:
On Sun, 2009-02-15 at 12:10 -0700, Gene Steinberg wrote:
This is sounding similar to the problem I have with my setup:
1. High CPU usage.
2. Can't kill IMAP.
kill -9 doesn't work for imap processes? You didn't mention this before.
I'm using CentOS 5.2 64-bit version
On Feb 15, 2009, at 12:53 PM, Seth Mattinen wrote:
Or it's I/O locked on the filesystem i.e. NFS server went away or
something else. What state ate the un-killable processes in? (Z, D,
S, etc.)
~Seth
I'd have to switch back to Dovecot in order to test for this, and
arrange to have
On Sun, 2009-02-15 at 12:48 -0700, Gene Steinberg wrote:
Here's the kernel info on my box:
Linux server.paracastworld.net 2.6.27.9rootserver-20081216a #1 SMP Tue
Dec 16 02:29:13 EST 2008 x86_64
So that's a buggy kernel?
Or is the 2.6.27.9 version better than 2.6.27 in this regard?
just again to the list wasnt in reply
Robert Schetterer schrieb:
Hi Gene , small tips depending suse
Gene Steinberg schrieb:
On Feb 14, 2009, at 9:57 AM, agent59624285 wrote:
I have this EXACT same problem after upgrading to SuSE 11.1, which
uses this
exact kernel version!!
After
On Feb 15, 2009, at 1:16 PM, Timo Sirainen wrote:
2.6.27.9 is buggy. I'm pretty sure upgrading the kernel will fix your
problem.
Would this be a simple yum upgrade to deliver? I don't want to cause
worse difficulties.
Peace,
Gene
On Sun, 2009-02-15 at 13:42 -0700, Gene Steinberg wrote:
On Feb 15, 2009, at 1:16 PM, Timo Sirainen wrote:
2.6.27.9 is buggy. I'm pretty sure upgrading the kernel will fix your
problem.
The yum upgrade function doesn't produce any updates.
Your kernel version looks like it's
It was likely compiled by the host/DC then, so it would not be a good
idea to change it.
Peace,
Gene
On Feb 15, 2009, at 2:19 PM, Timo Sirainen t...@iki.fi wrote:
On Sun, 2009-02-15 at 13:42 -0700, Gene Steinberg wrote:
On Feb 15, 2009, at 1:16 PM, Timo Sirainen wrote:
2.6.27.9 is buggy.
I have running the older debian/sid dovecot 1:1.0.15-2.3 again, now with
kernel 2.6.27-10.slh.1-sidux-686 and the issue seems to be fixed. So I
recommend to use at least 2.6.27.10.
Bye, Arno.
On Dec 15, 2008, at 1:00 PM, Arno Wald wrote:
A new status report regarding this issue:
Dovecot on my PC in the office is still running fine with kernel
2.6.26.
Dovecot with the latest kernel 2.6.27-9.slh.1-sidux-686 on my PC at
home did show the unkillable imap processes after a few
A new status report regarding this issue:
Dovecot on my PC in the office is still running fine with kernel 2.6.26.
Dovecot with the latest kernel 2.6.27-9.slh.1-sidux-686 on my PC at home
did show the unkillable imap processes after a few minutes.
Now I am running dovecot compiled without
Timo Sirainen wrote:
One more thing you could try: Does the hang happen if you use configure
--with-notify=dnotify ?
I do not know if this is still interesting. But after notify=none did
run for more than 3 hours without any problems, I am now testing dnotify
since approximately 30 minutes
On Mon, 2008-12-15 at 12:00 +0100, Arno Wald wrote:
So where are kernel issues reported? I will try to find out.
Linux kernel mailing list is probably the best place. I could also write
a summary mail about this and Cc it to you all who have had the problem.
signature.asc
Description: This is
Timo Sirainen wrote:
One more thing you could try: Does the hang happen if you use configure
--with-notify=dnotify ?
I first will keep the current version running for some hours to be more
sure it really does not make problems. After this I can test it with
dnotify.
Thanks,
Arno
Timo Sirainen wrote:
On Mon, 2008-12-15 at 12:00 +0100, Arno Wald wrote:
So where are kernel issues reported? I will try to find out.
Linux kernel mailing list is probably the best place. I could also write
a summary mail about this and Cc it to you all who have had the problem.
I would
So where are kernel issues reported? I will try to find out.
Linux kernel mailing list is probably the best place. I could also write
a summary mail about this and Cc it to you all who have had the problem.
Please cc me on it, I'd rather not have to subscribe to the lkml again.
Timo Sirainen wrote:
Or does it make more sense to try another kernel first?
I guess that could also help.
I started testing this with another kernel (2.6.26-6.slh.1-sidux-686).
Until now (the last 15 hours) no such failing imap process did show up.
So I guess it happens with 2.6.27
On Sat, 2008-12-13 at 11:33 +0100, Arno Wald wrote:
Timo Sirainen wrote:
Or does it make more sense to try another kernel first?
I guess that could also help.
I started testing this with another kernel (2.6.26-6.slh.1-sidux-686).
Until now (the last 15 hours) no such failing imap
The other guy who also had a problem was using 2.6.27. If the 3rd guy
also replies that he's using 2.6.27 then that's pretty clearly the
problem. Might be worth asking about in Linux kernel mailing list.
We've had something similar happen on 2.6.24. Over time processes would
take more and more
Cor Bosman wrote:
It seemed to be NFS related in our case.
Is your Maildir directory mounted via NFS?
I am using NFS-mounts, but not in connection with dovecot.
Greetings,
Arno
On Sat, December 13, 2008 5:43 am, Timo Sirainen wrote:
The other guy who also had a problem was using 2.6.27. If the 3rd guy
also replies that he's using 2.6.27 then that's pretty clearly the
problem. Might be worth asking about in Linux kernel mailing list.
Has anyone reported this over on
On Sat, 2008-12-13 at 09:23 -0500, David Rosenstrauch wrote:
On Sat, December 13, 2008 5:43 am, Timo Sirainen wrote:
The other guy who also had a problem was using 2.6.27. If the 3rd guy
also replies that he's using 2.6.27 then that's pretty clearly the
problem. Might be worth asking about
David Rosenstrauch wrote:
Has anyone reported this over on LKML yet? Or filed a bug?
I did not yet. First I would like to test my self compiled dovecot
without inotify against 2.6.27. Second I do not know where and how to
report kernel issues. (Also I am a little bit afraid of the whole
Timo Sirainen wrote:
Anyway, Arno's ps output showed the process to be in R state, not in D
It is definitely the R state.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
6717 arno 20 0 2964 1608 1192 R 100 0.2 1158:05 imap
btw: I have switched from imaps to
Timo Sirainen wrote:
You could see if compiling Dovecot without inotify/dnotify support would
help. I can't really think of anything else.
I would like to try this and report the result. But there are so many
configure-options that I do not know which options (and how) I should
dis/enable.
On Dec 12, 2008, at 6:02 PM, Arno Wald wrote:
Timo Sirainen wrote:
You could see if compiling Dovecot without inotify/dnotify support
would
help. I can't really think of anything else.
I would like to try this and report the result. But there are so many
configure-options that I do not
On Thu, 2008-12-11 at 11:36 +0100, Arno Wald wrote:
I am having a problem with my dovecot-daemon. It is forking one or more
(I saw up to perhaps 8 of them) imap processes under my user name. These
processes are consuming a lot of CPU time and are not killable:
PID USER PR NI VIRT
Timo Sirainen wrote:
If you can't kill a process with -9, the bug is in the kernel and
Do you have an idea, where and how I could report this to? (against the
kernel package?). Perhaps I try an original debian kernel instead the
sidux kernel first.
there's nothing Dovecot can do about it. User
Hi,
On Thu, 11 Dec 2008, Arno Wald wrote:
Timo Sirainen wrote:
If you can't kill a process with -9, the bug is in the kernel and
If there's is a blocked IO operation, like lost nfs mount point, processes
appear unkillable. As soon as the share is back, the processes die.
I've
seen this
If you can't kill a process with -9, the bug is in the kernel and
there's nothing Dovecot can do about it. User spaces processes can't
create unkillable processes unless something's broken.
It just means the process is doing an uninterruptable sleep (in BSD notation, a
tsleep() without PCATCH
On Thu, 2008-12-11 at 23:08 +0100, Edgar Fuß wrote:
If you can't kill a process with -9, the bug is in the kernel and
there's nothing Dovecot can do about it. User spaces processes can't
create unkillable processes unless something's broken.
It just means the process is doing an
34 matches
Mail list logo
