I'm having this same issue in one of my servers since I updated my Dovecot
from 1.2.4 to 1.2.5. The problem still with 1.2.6 too.
I cannot find what is triggering the problem, but it happens aleatory and I
need to restart the dovecot daemon to make the service run properly.
My info:
On Oct 30, 2009, at 7:08 PM, Victor Benincasa wrote:
I'm having this same issue in one of my servers since I updated my
Dovecot from 1.2.4 to 1.2.5. The problem still with 1.2.6 too.
Today I started thinking it has to be because some file descriptor is
opened as fd 5 initially, but it's
We've had this reoccur twice this week. In both cases, it seems to hit a
swath of machines all within a few minutes. For some reason it's been
limited to the master serving pop3 only. In all cases, the logging
socket at fd 5 had gone missing.
I haven't applied the fd leak detection patch, but I
On Thu, 2009-10-29 at 12:08 -0700, Brandon Davidson wrote:
I haven't applied the fd leak detection patch, but I do have lsof output
and a core file available here:
http://uoregon.edu/~brandond/dovecot-1.2.6/
There's no 0,12 in the lsof list.. Annoying, I can't seem to find what
it is. 0,10 is
If this really started happening only with v1.2.4 - v1.2.5, the only
change that looks anything like it could have to do with this problem is
the attached patch. I guess you could try reversing it and seeing if it
helps..
--- /home/timo/m/dovecot-1.2.4/src/master/main.c 2009-05-20
Hi Timo,
-Original Message-
From: Timo Sirainen [mailto:t...@iki.fi]
On Thu, 2009-10-29 at 12:08 -0700, Brandon Davidson wrote:
I haven't applied the fd leak detection patch, but I do have lsof
output
and a core file available here:
http://uoregon.edu/~brandond/dovecot-1.2.6/
On Thu, 2009-10-29 at 14:03 -0700, Brandon Davidson wrote:
You could also set login_process_per_connection=no and this should go
away, because then it only creates login processes at startup and
can't
fail randomly later.
Are there any downsides to doing this?
On Thu, Oct 22, 2009 at 07:58:22PM +0200, Marco Nenciarini wrote:
Timo Sirainen ha scritto:
On Thu, 2009-10-22 at 11:44 +0200, Marco Nenciarini wrote:
This morning it happened another time, another time during the daily
cron execution.
Oct 22 06:26:57 server dovecot: pop3-login: Panic:
Hi Marco,
On 10/22/09 1:50 AM, Marco Nenciarini mnen...@prato.linux.it wrote:
This morning it happened another time, another time during the daily
cron execution.
Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev
0.12 inode 1005
Oct 22 06:26:57 server dovecot:
Brandon Davidson ha scritto:
Hi Marco,
Let's see what Timo has to say about that log file bit. Since it seems to
happen to you fairly frequently, it might be worth enabling core dumps as
well?
You are right. I've just rebuilt my package with -g -O0 and enabled core
dumps.
Marco
--
This morning it happened another time, another time during the daily
cron execution.
Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev
0.12 inode 1005
Oct 22 06:26:57 server dovecot: dovecot: Temporary failure in creating
login processes, slowing down for now
Oct 22
On Thu, 2009-10-22 at 11:44 +0200, Marco Nenciarini wrote:
This morning it happened another time, another time during the daily
cron execution.
Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev
0.12 inode 1005
Can you apply the attached patch and see what it logs
Timo Sirainen ha scritto:
On Thu, 2009-10-22 at 11:44 +0200, Marco Nenciarini wrote:
This morning it happened another time, another time during the daily
cron execution.
Oct 22 06:26:57 server dovecot: pop3-login: Panic: Leaked file fd 5: dev
0.12 inode 1005
Can you apply the attached
: epoll_ctl(1, 5): Operation not permitted
Oct 15 03:41:51 oh-popmap5p dovecot: dovecot: Created login processes
successfully, unstalling
Oct 15 03:41:51 oh-popmap5p dovecot: pop3-login: Fatal:
io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted
Oct 15 03:41:51 oh-popmap5p dovecot: dovecot
Timo Sirainen ha scritto:
That's the pty's fd I think, probably from dovecot --exec-mail because
normally dovecot master process closes them at startup..
Did you check if two dovecot processes were running when this
happened?
This morning the problem showed again.
This is what I was able to
Marco Nenciarini ha scritto:
2) Imap and managesieve login and worker processes were working normally.
I only see this mistake now: the above statement is false, because the
subsequent log show an imap-login failure.
Sorry for this.
Marco
--
On Tue, Oct 06, 2009 at 11:59:02AM +0200, Marco Nenciarini wrote:
Timo Sirainen ha scritto:
That's the pty's fd I think, probably from dovecot --exec-mail because
normally dovecot master process closes them at startup..
Did you check if two dovecot processes were running when this
Timo Sirainen ha scritto:
On Wed, 2009-09-30 at 10:16 +0200, Marco Nenciarini wrote:
Sep 30 06:26:15 server dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
There is no additional information from Timo's patch,
Oh, annoying. There was a bug
On Thu, 2009-10-01 at 09:28 +0200, Marco Nenciarini wrote:
The only thing related I can think of is
http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 - did you have that
patch applied? Although I couldn't reproduce the problem even with that
reverted.
Another day, another failure, now
On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote:
Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
Has this happened to you again? Do you run expire-tool or some other
dovecot --exec-mail command? Or was there anything else run
Timo Sirainen ha scritto:
On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote:
Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
Has this happened to you again? Do you run expire-tool or some other
dovecot --exec-mail command
Timo Sirainen wrote:
On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote:
Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
Has this happened to you again? Do you run expire-tool or some other
dovecot --exec-mail command
On 10/1/2009, Mark Sapiro (m...@msapiro.net) wrote:
No, this hasn't happened again. It is dovecot 2.1.5
Ok, at first I thought this was just a silly typo, but...
The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had
been running for weeks with no problem. The problem started
Mark Sapiro wrote:
Timo Sirainen wrote:
On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote:
Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
Has this happened to you again? Do you run expire-tool or some other
dovecot --exec-mail
Charles Marcus wrote:
On 10/1/2009, Mark Sapiro (m...@msapiro.net) wrote:
No, this hasn't happened again. It is dovecot 2.1.5
Ok, at first I thought this was just a silly typo, but...
The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had
been running for weeks with no problem.
Timo Sirainen ha scritto:
On Sep 23, 2009, at 11:27 AM, Timo Sirainen wrote:
On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote:
First failure is:
Sep 23 06:26:14 server dovecot: pop3-login: Fatal:
io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted
That's really the first one
On Wed, 2009-09-30 at 10:16 +0200, Marco Nenciarini wrote:
Sep 30 06:26:15 server dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
There is no additional information from Timo's patch,
Oh, annoying. There was a bug in the function it used, this fixes
the same time from last server re start.
Last restart log is:
Sep 14 19:05:07 server dovecot: Dovecot v1.2.5 starting up (core dumps
disabled)
First failure is:
Sep 23 06:26:14 server dovecot: pop3-login: Fatal: io_loop_handle_add:
epoll_ctl(1, 5): Operation not permitted
After the attached
On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote:
First failure is:
Sep 23 06:26:14 server dovecot: pop3-login: Fatal:
io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted
That's really the first one, and there's no kind of an error from
dovecot master process? This sounds
On Sep 23, 2009, at 11:27 AM, Timo Sirainen wrote:
On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote:
First failure is:
Sep 23 06:26:14 server dovecot: pop3-login: Fatal:
io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted
That's really the first one, and there's no kind
Marco Nenciarini ha scritto:
Patch applied, now we must wait until the problem will show itself again
(may be a week or so).
The patch does not compile, need another parameter (may be 1024?)
Marco
--
-
|Marco
On Sep 23, 2009, at 12:11 PM, Marco Nenciarini wrote:
Marco Nenciarini ha scritto:
Patch applied, now we must wait until the problem will show itself
again (may be a week or so).
The patch does not compile, need another parameter (may be 1024?)
Oh, sorry. Use io-fd for the second one too.
Timo Sirainen wrote:
On Sep 23, 2009, at 11:17 AM, Marco Nenciarini wrote:
First failure is:
Sep 23 06:26:14 server dovecot: pop3-login: Fatal:
io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted
That's really the first one, and there's no kind of an error from
dovecot master
33 matches
Mail list logo
