El 31/08/11 12:31, Angel L. Mateo escribió:
* When openldap closes the connection because of the idle timeout, it
sends a FIN packet. When dovecot needs the connections, it simply opens
a new connection (without any log message).
* When my load balancer closes the connection, it doesn't send an
El 31/08/11 08:54, Angel L. Mateo escribió:
El 30/08/11 11:41, Timo Sirainen escribió:
Yeah, that happens if the disconnection is noticed at the time when
user is trying to authenticate. But if the disconnection is noticed
immediately when there are no user requests, there is also no message
lo
El 30/08/11 11:41, Timo Sirainen escribió:
Yeah, that happens if the disconnection is noticed at the time when user is
trying to authenticate. But if the disconnection is noticed immediately when
there are no user requests, there is also no message logged about it.
So, there must be any prob
On 30.8.2011, at 9.38, Angel L. Mateo wrote:
>> Why? If LDAP server idle-disconnects after 61 seconds and before NAT
>> timeout then Dovecot doesn't log anything about it.
>>
> I have tried this. My LDAP server closed the connection, but dovecot
> logged the message. I guess that, for dove
El 30/08/11 05:13, Timo Sirainen escribió:
On Mon, 2011-08-29 at 11:44 +0200, Angel L. Mateo wrote:
Is there any way to configure ldap connection with a keepalive, so I
don't need a reconnection?
Nope. But you could configure your LDAP server to idle-disconnect after
some amount of tim
On Mon, 2011-08-29 at 11:44 +0200, Angel L. Mateo wrote:
> >>Is there any way to configure ldap connection with a keepalive, so I
> >> don't need a reconnection?
> >
> > Nope. But you could configure your LDAP server to idle-disconnect after
> > some amount of time.
> >
> I know it, but c
auth: Error: LDAP: Connection lost to
LDAP server, reconnecting (1 requests, 3603 idle secs)
Ah. So this is noticed only when Dovecot tries to use the LDAP
connection that it's been disconnected.
Is there any way to configure ldap connection with a keepalive, so I
don't need
ed the patch. It confirms my hypothesis, the connection is
> closed by my load balancer:
>
> Aug 26 12:55:27 myotis31 dovecot: auth: Error: LDAP: Connection lost to
> LDAP server, reconnecting (1 requests, 3603 idle secs)
Ah. So this is noticed only when Dovecot tries to use the LDAP
co
uch a feature :) See what it logs with
attached patch.
I have tried the patch. It confirms my hypothesis, the connection is
closed by my load balancer:
Aug 26 12:55:27 myotis31 dovecot: auth: Error: LDAP: Connection lost to
LDAP server, reconnecting (1 requests, 3603 idle secs)
Is there an
El 25/08/11 12:10, Timo Sirainen escribió:
On 25.8.2011, at 13.04, Angel L. Mateo wrote:
Aug 24 23:07:32 myotis28 dovecot: auth-worker(default): LDAP: Connection lost
to LDAP server, reconnecting
I have seen in the mail list a patch for 1.2
(http://hg.dovecot.org/dovecot-1.2/rev/355d
On 25.8.2011, at 13.04, Angel L. Mateo wrote:
> Aug 24 23:07:32 myotis28 dovecot: auth-worker(default): LDAP: Connection lost
> to LDAP server, reconnecting
>
> I have seen in the mail list a patch for 1.2
> (http://hg.dovecot.org/dovecot-1.2/rev/355d5a40f7a7) to ignore these logs
> when
Hello,
I continue debugging my problems with my update to dovecot 2.x :-(
I have dovecot 2.0.13 running in ubuntu 10.04 (lucid) x64. My users are
in a ldap directory. The problem is that I have a lot of errors like:
Aug 24 23:07:32 myotis28 dovecot: auth-worker(default): LDAP: Connec
12 matches
Mail list logo
