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 > >happened? > > This morning the problem showed again. > > This is what I was able to discover: > > 1) There was only one master process. > 2) Imap and managesieve login and worker processes were working normally. > 3) There was no pop3/pop3-login. > > After the last time I've modified my root crontab to execute the > expire-tool every minute, trying to trigger the problem in another time > of the day, but the first failure is > > Oct 6 06:26:02 delta01 dovecot: imap-login: Panic: Leaked file fd 5: > dev 0.12 inode 1005 > Oct 6 06:26:02 delta01 dovecot: dovecot: Temporary failure in creating > login processes, slowing down for now > Oct 6 06:26:02 delta01 dovecot: dovecot: child 21216 (login) killed > with signal 6 (core dumps disabled) > > As you can see this time is the login process of an imap connection, so > I can state that the problem is not related to pop3 and nor to expire > plugin. > > Probably the imap connections that I see were there before the problem > was triggered. > > So the only remaining thing in daily log rotation that can be the > trigger of the problem is the heavy cpu/io load due to daily maintenance. > > The last weird thing is that this time I have simply asked dovecot to > reload its configuration and the problem is vanished. > > I hope this is enough to figure out what was happened. >
On the other hand, I have not seen a recurrence since my initial report. At this point, dovecot has been running without interruption for over 9 days. I intend to install 1.2.6 tomorrow. -- Mark Sapiro mark at msapiro net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan