On Sat, Aug 17, 2002, Sam Varshavchik <mrs...@courier-mta.com> wrote:
On Sat, Aug 17, 2002 at 11:55:10AM -0500, Matt Pavlovich wrote:
The LDAP server has been running since Aug 06, with no signs of going
down. Below are some log files from Error 400 instances.
Well, the LDAP client is unable to query the server, that's the bottom line.
You'll need to figure out why.
I found what may be the issue... the LDAP Server had the idletimeout
setting to 7200 (seconds). Perhaps the LDAP server was closing idle
authdaemon and ldapaliasd connections.
Are the authdaemon and ldapaliasd resilient to the server unexpectedly
closing connections?
This is considered as a server crash. A minute or so later they'll try to
reconnect, until then all requests are going to be deferred.
There's your answer. The whole purpose of authdaemon and ldapaliasd is to
maintain persistent, long term connections to the database, in order to
eliminate the overhead of connecting and reconnecting to the database for each
message.
All TCP servers must have a timeout.
Is there something we can do as a keepalive for idle LDAP connections?
JE
10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Error: 400 Se...
