On 07 Mar 2011, at 17:17, Timo Sirainen wrote:
> On Mon, 2011-03-07 at 13:40 +0200, Thierry de Montaudry wrote:
>>>>> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3)
>>>>> failed: Resource temporarily unavailable
> ..
>>> Do you see any warning messages in logs containing "client connections are
>>> being dropped"?
>>>
>> I did not see it on any machines.
>
> Hmh. Could you upgrade to 2.0.11? It splits the two causes of "Resource
> temporarily unavailable" errors to two separate error messages. It would
> help figuring out the problem.
>
>> But for this specific one, I got the following after those errors, before
>> restarting dovecot:
>>
>> Mar 7 11:20:09 web4 dovecot: pop3(x@y): Error:
>> net_connect_unix(/var/run/dovecot/dict) failed: Connection refused
>> Mar 7 11:20:11 web4 dovecot: pop3-login: Error: read(pop3) failed:
>> Connection reset by peer
>> Mar 7 11:20:11 web4 dovecot: pop3-login: Error: read(pop3) failed:
>> Connection reset by peer
>> Mar 7 11:20:11 web4 dovecot: pop3-login: Error: read(pop3) failed:
>> Connection reset by peer
>> Mar 7 11:20:11 web4 dovecot: pop3-login: Error: read(pop3) failed:
>> Connection reset by peer
>
> This looks like processes started dying.
>
As it is happening at least once a day, is there anything I can do to trace it?
and whatever I'll do, will it slow down those machines?
