[Dovecot] assertion failed
I'm getting these in my log:
Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child 24406 (login) killed with signal 6
This is dovecot-1.0.2 -- is this something to worry about?
-- 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 There are two ways to write error-free programs. Only the third one works.
On Tue, 2007-07-17 at 21:06 +0200, Ralf Hildebrandt wrote:
I'm getting these in my log:
Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child 24406 (login) killed with signal 6
This is dovecot-1.0.2 -- is this something to worry about?
Do you see "Disconnected: Connection queue full" messages in your logs?
- Timo Sirainen <tss@iki.fi>:
On Tue, 2007-07-17 at 21:06 +0200, Ralf Hildebrandt wrote:
I'm getting these in my log:
Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child 24406 (login) killed with signal 6
This is dovecot-1.0.2 -- is this something to worry about?
Do you see "Disconnected: Connection queue full" messages in your logs?
Yes, at the very same times the other messages are appearing - from my logs:
Jul 17 11:40:42 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=192.168.232.149, lip=141.42.4.250 Jul 17 11:51:12 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250
-- 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 How many viruses must arrive before people realize, that M$ is just not ready for the enterprise?
On Tue, 2007-07-17 at 22:34 +0200, Ralf Hildebrandt wrote:
- Timo Sirainen <tss@iki.fi>:
On Tue, 2007-07-17 at 21:06 +0200, Ralf Hildebrandt wrote:
I'm getting these in my log:
Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child 24406 (login) killed with signal 6
This is dovecot-1.0.2 -- is this something to worry about?
Do you see "Disconnected: Connection queue full" messages in your logs?
Yes, at the very same times the other messages are appearing - from my logs:
Jul 17 11:40:42 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=192.168.232.149, lip=141.42.4.250 Jul 17 11:51:12 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250
You might want to increase the number of simultaneous login processes if you're reaching this limit. http://wiki.dovecot.org/LoginProcess
Of course it shouldn't crash either, I'll see if I can get that fixed.
- Timo Sirainen <tss@iki.fi>:
Jul 17 11:40:42 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=192.168.232.149, lip=141.42.4.250 Jul 17 11:51:12 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250
You might want to increase the number of simultaneous login processes if you're reaching this limit. http://wiki.dovecot.org/LoginProcess
I already did that:
login_process_per_connection: no login_process_size: 64 login_max_processes_count: 256 login_max_connections: 128
Should I go higher? I have approximately 70 IMAP logins/minute on average, but peaks of up to 140 logins/minute.
Of course it shouldn't crash either, I'll see if I can get that fixed.
:)
-- 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 The Pope has said this war is wrong, that it is a Sin. The Pope! But even worse, the Dixie Chicks have now come out against you! How bad does it have to get before you realize that you are an army of one on this war? -- Michael Moore
participants (2)
-
Ralf Hildebrandt
-
Timo Sirainen