This morning dovecot stopped allowing pop3 logins. In the logs I found the messages below Is there a config value for the max open files ? Dec 7 10:00:22 frigga dovecot: execv(/usr/local/libexec/dovecot/pop3) failed: Too many open files Dec 7 10:01:14 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:43 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:45 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:39 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:41 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:50 frigga dovecot: pipe() failed: Too many open files Dec 7 10:05:00 frigga dovecot: pipe() failed: Too many open files Dec 7 10:05:02 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:06 frigga dovecot: pipe() failed: Too many open files Dec 7 10:07:48 frigga dovecot: pipe() failed: Too many open files Dec 7 10:08:05 frigga dovecot: pipe() failed: Too many open files
Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco)
2007-Dec-07 14:24 UTC
[Dovecot] open files
Most likely you hit this threshold: [root at host ~]# cat /proc/sys/fs/file-max 380081 Check the current usage here: [root at host ~]# cat /proc/sys/fs/file-nr 2145 0 380081 -----Original Message----- From: dovecot-bounces+joallesi=cisco.com at dovecot.org [mailto:dovecot-bounces+joallesi=cisco.com at dovecot.org] On Behalf Of Steve Heaven Sent: Friday, December 07, 2007 6:24 AM To: dovecot at dovecot.org Subject: [Dovecot] open files "Is there a config value for the max open files ?"
On Fri, 2007-12-07 at 09:24 -0500, Joe Allesi -X (joallesi - Coyote Creek Consulting at Cisco) wrote:> Most likely you hit this threshold: > > [root at host ~]# cat /proc/sys/fs/file-max > 380081 > > Check the current usage here: > > [root at host ~]# cat /proc/sys/fs/file-nr > 2145 0 380081 >I doubt it, the current figures are: # cat /proc/sys/fs/file-nr 2112 0 24748 # cat /proc/sys/fs/file-max 24748 So we are using less than a tenth of the available handles -- thorNET Internet Services, Consultancy & Training www.thornet.co.uk
On Fri, 2007-12-07 at 11:23 +0000, Steve Heaven wrote:> This morning dovecot stopped allowing pop3 logins. In the logs I found > the messages below > Is there a config value for the max open files ? > > > Dec 7 10:00:22 frigga dovecot: execv(/usr/local/libexec/dovecot/pop3) > failed: Too many open files > Dec 7 10:01:14 frigga dovecot: pipe() failed: Too many open filesYou probably had lots and lots of pop3 processes running, overflowing the number of available fds for logging. v1.1 gives a warning about this at startup. Change your ulimit or settings so that "ulimit -n" before starting Dovecot gives a somewhat larger number than max_mail_processes + login_max_processes_count. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071207/78f9aba7/attachment-0002.bin>
On Fri, 2007-12-07 at 16:38 +0200, Timo Sirainen wrote:> > Change your ulimit or settings so that "ulimit -n" before starting > Dovecot gives a somewhat larger number than max_mail_processes + > login_max_processes_count.OK, thanks -- thorNET Internet Services, Consultancy & Training www.thornet.co.uk