Hi In a short period of time, we had some (and different) problems that were solved restarting Dovecot. Killing the process 'dovecot' and restarting it again takes less than 1 second, and it doesn't kill the running sessions, so I set up a cron job that restarted it every couple of hours, without disturbing users. Yo can do it once a day (in the night, for example) and don't run any risk.

Regards.

Obantec Support wrote:

Hi

Still running 1.0 stable (an old release i know but until i see more stable reports on beta7 i will hold out).

last night is the first time in months the dovecot has died. maillog has repeated lines of this.

Apr 16 02:31:37 proteus2 dovecot: pipe() failed: Too many open files

dovecot.log just shows last login Apr 16 02:31:36 Info: pop3-login: Login: username [IP]

i restarted it

Apr 16 08:38:04 Info: Dovecot v1.0-stable starting up

and now it seems ok.

anyone got a monitor script for watching the dovecot daemon and send a start if it dies?

Mark

-- +----------------------------------------------^-----------------------+ | Luis Meléndez Aganzo ^ Email: luism@uco.es | | Servicio de Informática ^ Tlf: 34-(9)57-211022 | | Área de Sistemas ^ Fax: 34-(9)57-218116 | | Universidad de Córdoba (SPAIN) ^ http://www.uco.es | +----------------------------------------------^-----------------------+

On Sun, 2006-04-16 at 08:49 +0100, Obantec Support wrote:

Hi

Still running 1.0 stable (an old release i know but until i see more stable reports on beta7 i will hold out).

last night is the first time in months the dovecot has died. maillog has repeated lines of this.

Apr 16 02:31:37 proteus2 dovecot: pipe() failed: Too many open files

Since 1.0.beta6 Dovecot should be able to restore itself after this problem when more file descriptors are available. Of course if it's leaking the fds for some reason then it can't really fix itself without restarting..