search for: idle_timeout_msec

Sometimes my redis connection times out, both for pop3, imap and lmtp. I have no idea why, when I do a "doveadm quota recalc -u" it works just fine? I'm thinking the connection is lost somehow and not retried? Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: redis: Lookup timed out in 30.000 secs Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: Internal quota calculation error Apr 06

...of a random pattern. > 3) Is there some firewall between Dovecot and Redis that closes idling > connections and causes them to hang? Dovecot doesn't close idle Redis > connections, although I suppose it would be useful too. The attached > patch probably helps here by adding a new idle_timeout_msecs setting. > I didn't finish testing it. No firewall at all. I'm unsure if redis closes idle connections, that could be the cause of it. What about the issue of lmtp saving the mail, but sending an error back to Director? Thanks :) -- Tom

...30e9b423 in auth_request_proxy_host_lookup (callback=0x55c930e9cab0 <auth_request_handler_proxy_callback>, host=0x55c930eca584 "", request=0x55c932881628) at auth-request.c:2584 dns_set = {dns_client_socket_path = 0x55c930ec5eaf "dns-client", timeout_msecs = 10000, idle_timeout_msecs = 0, ioloop = 0x0, event_parent = 0x0} value = <optimized out> secs = 32551 #10 auth_request_proxy_finish (request=request at entry=0x55c932881628, callback=callback at entry=0x55c930e9cab0 <auth_request_handler_proxy_callback>) at auth-request.c:2631 host = 0x5...

Hi, currently we deploying Dovecot as imap/pop3 proxy. Every few minutes some panic/assert occurred (we connect roughly 7k - 8k user at one imap proxy with a connection rate of 200/s). We activate core dumps. Concerning the sensitive information in the dump we would prefer to not share the dump (e.g. i found our ssl private key in the dump). Log/Stack trace: Mar 30 15:54:06 imap16 dovecot: