[Dovecot] avoid log message when using nagios check

[Daniel Parthey]

Am 10.07.2013 21:41, schrieb Timo Sirainen:
> On 10.7.2013, at 22.39, Daniel Parthey<d.parthey at metaways.de>  wrote:
>
>>> So it would have to disable logging also for the logout message after
>>> login.. Can those load balancers be configured to send these kind of
>>> extra XCLIENT/ID commands? Is it really worth the effort that it really
>>> works in enough systems?
>>
>> No. It does simple TCP connects, doesn't know about IMAP at all and won't send any string, it just checks if the TCP port is available. Would it be a problem to remove the log message altogether, at least for trusted IPs or make it a warning, not an error. What is so bad with TCP connects/disconnects without any IMAP traffic, especially when they originate from trusted IPs?
>
> They are regular info messages, not errors or warnings..
>

You're right, TCP connections don't seem to be a real problem here.

I confused it with the following messages, we get every few minutes in 
the dovecot-director.log, but I'm not sure of their origin yet,
there are some other imap proxies/balancer in front of the director:

Jul 10 21:51:46 10.129.3.233 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 21:51:49 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 21:54:46 10.129.3.233 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 21:56:22 10.129.3.233 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 21:57:51 10.129.3.200 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 21:59:23 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:00:48 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:03:47 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:06:51 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:11:14 10.129.3.200 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:12:52 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:15:50 10.129.3.200 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:15:50 10.129.3.233 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:24:51 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:24:53 10.129.3.200 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:35:21 10.129.3.200 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:39:52 10.129.3.213 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer
Jul 10 22:41:22 10.129.3.233 dovecot: director: Error: read(login 
connection) failed: Connection reset by peer

Regards
Daniel
-- 
Dipl.-Inf. Daniel Parthey
System Engineer
Metaways Infosystems GmbH
Pickhuben 2, D-20457 Hamburg

E-Mail: d.parthey at metaways.de
Web:    http://www.metaways.de

Metaways Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht Lübeck HRB 4508 AH
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele