my issue is that i have to use the RedHat ES 4 Openldap package. I have the same openldap on to servers. one is working properly. the other have this err=52 error after an undefined time !!!!
i realy don't understand why openldap "is shutting down".
Thnaks for your help
Thomas
Message du 30/03/07 à 16h19 De : "Aaron Richton" A : "jerrrry@voila.fr" Copie à : openldap-software@openldap.org Objet : Re: err=52
back-ldap has had an unbelievable amount of work done to it since 2.2.13. Case on point, I started using it seriously around 2.3.19, and there's been a lot of work done since then. Upgrade to 2.3.34 and try again. See http://www.openldap.org/software/release/changes.html for details.
On Fri, 30 Mar 2007, jerrrry@voila.fr wrote:
Hi all, i'm using openldap 2.2.13 as a proxy to an other ldap server. it works and after few days, authentications doesn't work any more. and i have an error 52 in my ldap log: ar 29 17:51:13 guardsdef1 slapd[23444]: conn=4 op=5 SRCH base="ou=personnes,o=st" scope=2 deref=3 filter="(&(objectClass=*)(uid=n588t67))" Mar 29 17:51:13 guardsdef1 slapd[23444]: conn=4 op=5 SRCH attr=uid Mar 29 17:51:13 guardsdef1 slapd[23444]: conn=4 op=5 SEARCH RESULT tag=101 err=52 nentries=0 text= Mar 29 17:51:13 guardsdef1 slapd[23444]: conn=4 op=5 SEARCH RESULT tag=101 err=52 nentries=0 text=
this error means: LDAP_UNAVAILABLE: Indicates that the LDAP server cannot process the client's bind request, usually because it is shutting down.
my slapd conf: database ldap suffix o=sg uri ldaps://ldap.s45ame.iioup.soen
Do you have any idea why open ldap "is shutting down" ?
thank you for your help
Thomas
mys issue
On Mon, 2 Apr 2007, jerrrry@voila.fr wrote:
my issue is that i have to use the RedHat ES 4 Openldap package.
Then your issue should be directed to support.redhat.com...
I'm pretty sure that your "err=52" is ITS#4429, reported against 2.3.20 and fixed in 2.3.21 (April, 2006).
RedHat obviously doesn't care about patches that affect actual sites (such as mine and yours), even given a full year to integrate them. I'd highly suggest using an alternative software source that has acceptable support. (I would claim that the mere fact that you're running into a known and long-fixed bug does not constitute "acceptable support" if you're running an OpenLDAP server.) But if you "have to use" the RedHat ES 4 package, you'll have to take it up with them that their laziness is causing you production issues.
openldap-software@openldap.org