[Dovecot] imap-login: Disconnected: Connection queue full
I'm getting "imap-login: Disconnected: Connection queue full:" messages like these:
May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250
Should I worry about these messages or are they of informational character only?
Does it mean that the imap-login encountered more than "login_max_connections" and thus a new process had to be spawned?
Is there a parameter I should be changing (config below)
# /usr/local/sbin/dovecot --version 1.0.0
---- snip --- # /usr/local/etc/dovecot.conf protocols: imap imaps pop3s ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no login_process_size: 64 login_max_connections: 32 verbose_proctitle: yes mail_location: maildir:~/Maildir mail_read_mmaped: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle netscape-eoh imap_client_workarounds(imap): outlook-idle netscape-eoh imap_client_workarounds(pop3): outlook-idle pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v-%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota: maildir:ignore=Trash ---- snip ---
-- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk@charite.de
On Wed, 2007-05-16 at 12:42 +0200, Ralf Hildebrandt wrote:
I'm getting "imap-login: Disconnected: Connection queue full:" messages like these:
May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250
Should I worry about these messages or are they of informational character only?
Does it mean that the imap-login encountered more than "login_max_connections" and thus a new process had to be spawned?
No. It means that it disconnected a client that wasn't yet logged in because login_max_connections was reached. It should happen only if login_max_processes_count was reached. Perhaps there's still a bug somewhere in there.. How many imap-login processes do you have running? Increasing login_processes_count probably helps for now.
login_process_per_connection: no login_max_connections: 32
With these settings it should have allowed 32*128 connections / ssl proxies until the connection queue full error would have happened.
- Timo Sirainen <tss@iki.fi>:
No. It means that it disconnected a client that wasn't yet logged in because login_max_connections was reached. It should happen only if login_max_processes_count was reached. Perhaps there's still a bug somewhere in there.. How many imap-login processes do you have running? Increasing login_processes_count probably helps for now.
root@postamt:~# ps auxwww |grep "imap \[" |wc -l 616 root@postamt:~# ps auxwww |grep "imap-login" |wc -l 14
So I have 616 "imap" processes and 14 imap-login processes. Each of the 14 handles up to 32 auth requests. And if I get this right, NEW imap-login processes are spawned automatically when the need arises. Correct?
So I'm well below my limit of 128 imap-login processes. Or do I have to count other *-login processes as well?
-- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk@charite.de
On Wed, 2007-05-16 at 14:17 +0200, Ralf Hildebrandt wrote:
- Timo Sirainen <tss@iki.fi>:
No. It means that it disconnected a client that wasn't yet logged in because login_max_connections was reached. It should happen only if login_max_processes_count was reached. Perhaps there's still a bug somewhere in there.. How many imap-login processes do you have running? Increasing login_processes_count probably helps for now.
root@postamt:~# ps auxwww |grep "imap \[" |wc -l 616 root@postamt:~# ps auxwww |grep "imap-login" |wc -l 14
So I have 616 "imap" processes and 14 imap-login processes. Each of the 14 handles up to 32 auth requests. And if I get this right, NEW imap-login processes are spawned automatically when the need arises. Correct?
That's correct, but if you're getting those kind of errors I guess there are some bugs. Are all those imap connections using SSL/TLS?
So I'm well below my limit of 128 imap-login processes. Or do I have to count other *-login processes as well?
The limits are counted separately for imap-logins and pop3-logins.
- Timo Sirainen <tss@iki.fi>:
That's correct, but if you're getting those kind of errors I guess there are some bugs. Are all those imap connections using SSL/TLS?
# grep "Connection queue full" /var/log/pop3d-imapd.log |grep TLS|wc -l 31 # grep "Connection queue full" /var/log/pop3d-imapd.log |wc -l 104
So, 31 of 104 are TLS.
-- Ralf Hildebrandt (Ralf.Hildebrandt@charite.de) plonk@charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de To rephrase, spam is not the answer. Spam is the question. Death is not the answer, but pretty close to it.
participants (2)
-
Ralf Hildebrandt
-
Timo Sirainen