Patch SERVICE_FIRST_STATUS_TIMEOUT

[Timo Sirainen]

On 16 Mar 2015, at 19:24, Andre Helwig <a.helwig at heinlein-support.de> wrote:
> 
> Hi list,
> we had a lot of trouble with our Dovecot Replicating-Cluster
> installation authenticating against LDAP Service.
> 
> We ran in a timeout and what happened was that we got more and more
> search requests running against on our ldap server.
> 
> And on the dovecot site the process got killed after a couple of
> seconds. So we ran into a race condition and our LDAP Server was under
> heavy load.
> We got a log entry like this: "Initial status notification not received
> in 30 seconds, killing the process"

What process? auth process?

> So we had to apply the attached patch to our Source based Dovecot Cluster.
> 
> Could you please make a configurable Parameter for our Patched value?
> 
> That would be great to get this parameter Configurable.

That's the wrong solution though. A process initialization is supposed to take less than a second always. If something like LDAP initialization is taking minutes, this waiting should be done after the process initialization has finished.

I thought the LDAP initialization code was asynchronous though, unless you're using sasl_bind=yes or tls=yes?