Do you know what is Dovecot's default SQL query time out and with which parameter can I maybe increase that timeout?

Thanks for the hint regarding the userdb prefetch, that makes sense and I have now put the userdb prefetch before the userdb SQL as recommended.

Doing that I also noticed that in my /etc/dovecot/conf.d/10-auth.conf I still have the system user authentication enabled with this line:

!include auth-system.conf.ext

although I am using SQL only (PostgreSQL). Can I safely disable this line you think?

On Friday, January 30, 2015 9:45 AM, Steffen Kaiser skdovecot@smail.inf.fh-brs.de wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, 30 Jan 2015, ML mail wrote:

I was checking the errors on my mailbox server using "doveadm log errors" and found that around 2-3 times a day I get the following error:

Jan 29 22:14:43 auth: Error: auth worker: Aborted request: Lookup timed out

Any ideas if this is a bad sign? For example some timeout on my side which is too low or is it just an aborted connection from the side of the IMAP client?

1st bet is that the SQL query timed out. It is bad sign.

The configuration on my Dovecot mailbox server can be found here:

http://article.gmane.org/gmane.mail.imap.dovecot/80823

you should place userdb prefetch before userdb sql. The current order makes no sense. But this is not the source of your problem.

Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1

iQEVAwUBVMtDknz1H7kL/d9rAQIgHwf7BluhPtKfdZR31VoVsfyEgteQT0rAXE6r bsv96ToibGO+9gFjk3LM745FFJuFwiBsSCqRIrF4KxXBoI4wBY072JlLwnBjOh/C 57wwvVTw8DIPEkMin0cCOo/OLHXXaGs0h9vcQ86F/m4wnQTyMD1l2YYEdAITpoQM s+nqfzPiYfTSsHCOovEdb2L54VYpgJvTE8BXehdvd2sSpygaCZEV91R1ToxGZypy Y1gdd6YR6AIPiBQXdw0rlLJABiSHGwcV1s7g1xBz2exZguxfBDDuP97OPCU+D+c6 efVVqVoedJMi1311/jIYdtyxUjYUGYZXzsKcBCYuyYPWjQ82MdKyLw== =rbCo -----END PGP SIGNATURE-----

hi

I don't know if this is related but I also get quite a few of these error messages:

Jan 31 14:10:46 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer

my interpretation:

a) you have a very very bz network ... the other end cannot respond to incoming requests

even if your network is NOT bz, eg, no collision blinking on your hubs/switches, you are still having network problems

b) if all of your dovecot tests is on one host ... disconnect it from the network and see if dovecot's auth finishes its tasks

c) to clean up your network ... - use switches ... not hubs .... even inexpensive netgear switches is good enuff - use good 3-6' cat6e cables ... we'll assume the bldg's wiring is done to bldg specs - my guess, you're probably having cabling problems ) - separate slow devices from faster devices eg. separate printers onto its own network with a switch in between printers and everybody else - separate 10/100 devices from gigE devices ... do not mix them up on the same switch/hub c ya alvin

Jan 31 14:13:20 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Jan 31 14:13:20 auth: Warning: auth client 0 disconnected with 2 pending requests: Connection reset by peer Jan 31 14:13:22 auth: Warning: auth client 0 disconnected with 2 pending requests: EOF Jan 31 14:13:26 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer

maybe around 20-30 per day.

Am 01.02.2015 um 22:44 schrieb ML mail:

Thanks for your tip regarding the busy network.

I am using a one year old Cisco Catalyst 2960S (WS-C2960S-48TD-L) with cat6e cables and my network should not be overloaded as far as I know. My mailbox and mail proxy servers are on two different virtual machines on two different servers. It could be possible that it is something with the virtualization but my other VMs do not have any connection time outs or anything. I will keep on searching on the network side.

the busy network tip is nonsense since "Connection reset by peer" means nothing else as it says "the remote client lost connection for whatever reason" and that are most likely *mobile clients* and *bots*

Feb 1 20:24:17 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:24:46 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:25:18 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:26:01 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:26:45 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:27:34 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 20:37:04 mail dovecot: auth: Warning: auth client 0 disconnected with 2 pending requests: Connection reset by peer Feb 1 20:37:57 mail dovecot: auth: Warning: auth client 0 disconnected with 2 pending requests: Connection reset by peer Feb 1 21:26:39 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:27:49 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:28:33 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:28:51 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:29:35 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:30:19 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:31:03 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:31:39 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:31:47 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:32:31 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Feb 1 21:33:53 mail dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer

...

I don't know if this is related but I also get quite a few of these error messages:

Jan 31 14:10:46 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer

my interpretation:

a) you have a very very bz network ... the other end cannot respond to incoming requests

even if your network is NOT bz, eg, no collision blinking on your hubs/switches,
you are still having network problems

b) if all of your dovecot tests is on one host ... disconnect it from the network and see if dovecot's auth finishes its tasks

c) to clean up your network ... - use switches ... not hubs .... even inexpensive netgear switches is good enuff - use good 3-6' cat6e cables ... we'll assume the bldg's wiring is done to bldg specs - my guess, you're probably having cabling problems ) - separate slow devices from faster devices eg. separate printers onto its own network with a switch in between printers and everybody else - separate 10/100 devices from gigE devices ... do not mix them up on the same switch/hub c ya alvin

...

Jan 31 14:13:20 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Jan 31 14:13:20 auth: Warning: auth client 0 disconnected with 2 pending requests: Connection reset by peer Jan 31 14:13:22 auth: Warning: auth client 0 disconnected with 2 pending requests: EOF Jan 31 14:13:26 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer