On Fri, Mar 08, 2013 at 09:41:10AM -0800, Quanah Gibson-Mount wrote:
> >On a sufficiently idle system (say a test system which only receives
> >intermittent email messages) the processes that are connected to LDAP
> >may exit when idle for long enough, and then new connections will be
> >made later. The same happens on systems where some misguidedly runs
> >"postfix reload" frequently.
>
> This is not really the behavior I see from proxy:. For example, the
> connection I pasted from this morning:
Not all connections are necessarily from proxy processes, and not
all proxy processes are eternal.
> Mar 8 08:12:27 ldap01-zcs slapd[7644]: conn=29791 op=7801 SRCH
> attr=zimbraMailCanonicalAddress zimbraMailCatchAllCanonicalAddress
> Mar 8 08:12:27 ldap01-zcs slapd[7644]: conn=29791 op=7801 SEARCH
> RESULT tag=101 err=0 nentries=0 text=
> Mar 8 08:12:32 ldap01-zcs slapd[7644]: conn=29791 fd=84 closed
> (connection lost)
>
> You can see that postfix closed the connection (without sending an
> unbind) 5 seconds after operation 7801. Postfix has established 258
> connections since 4 am this morning, all of which it initiates a
> close on after some amount of time (i.e., the LDAP server is not the
> one closing the connection).
Postfix does not do "graceful shutdown" of database tables on exit.
When a process is done, it exits. What is your max_idle set to?
--
Viktor.
