Re: [Dovecot] PAM authentication problems
Timo Sirainen escreveu: On Oct 5, 2008, at 12:37 AM, Timo Sirainen wrote: On Oct 4, 2008, at 10:27 AM, Tom Lobato wrote: Oct 3 09:00:10 coan dovecot: auth(default): pam(rodrigo.botan,121.120.119.179): pipe() failed: Too many open files Set this to non-zero: # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 Oops, sorry, you're using v1.0.rc15 which doesn't have this setting. In that case I don't really know why it's failing. Look at /proc/`pidof dovecot-auth`/fd/. Where are all the file descriptors going? In any case I'd suggest upgrading to a newer version (from backports.org). That alone might fix the problem. great! I upgraded dovecot (with backports.org package) and now it works. I don`t know why it started to give such problems but the upgrade solved it. thank you very much, Timo! Tom Lobato
Re: [Dovecot] PAM authentication problems
On Oct 4, 2008, at 10:27 AM, Tom Lobato wrote: Oct 3 09:00:10 coan dovecot: auth(default): pam(rodrigo.botan,121.120.119.179): pipe() failed: Too many open files Set this to non-zero: # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] PAM authentication problems
On Oct 5, 2008, at 12:37 AM, Timo Sirainen wrote: On Oct 4, 2008, at 10:27 AM, Tom Lobato wrote: Oct 3 09:00:10 coan dovecot: auth(default): pam(rodrigo.botan,121.120.119.179): pipe() failed: Too many open files Set this to non-zero: # Number of auth requests to handle before destroying the process. This may # be useful if PAM plugins leak memory. #auth_worker_max_request_count = 0 Oops, sorry, you're using v1.0.rc15 which doesn't have this setting. In that case I don't really know why it's failing. Look at /proc/ `pidof dovecot-auth`/fd/. Where are all the file descriptors going? In any case I'd suggest upgrading to a newer version (from backports.org). That alone might fix the problem. PGP.sig Description: This is a digitally signed message part
