Dear Howard,

We didn't use back-ldap as proxy backend in the past, we had a very old ope= nldap and did use syncrepl.=20 Then we changed our IT Infrastructures and had to use ldap proxy. That was = around 3 months ago. So we tried with 2.4.26 coming from sles and there we had the problem..so w= e tried then with the latest release and with both it was the same.

Thanks a lot for your FIX. Actually it looks like working fine, the slapd of the ldap proxy didn't cra= sh anymore since 24 hours. No segfaults at the moment. We will monitor it next few days and weeks and if you like we can give you = again a feedback.

ITS#8173 fix SEGV after failed retry [openldap.git] / servers / slapd / back-ldap / bind.c

diff --git a/servers/slapd/back-ldap/bind.c b/servers/slapd/back-ldap/bind.= c index 598dae3..20197f3 100644 (file)

--- a/servers/slapd/back-ldap/bind.c +++ b/servers/slapd/back-ldap/bind.c @@ -271,6 +271,8 @@ retry:; =20 if ( ldap_back_retry( &lc, op, rs, LDAP_BACK_BIND_SERR ) ) { = =20 goto retry; } + if ( !lc ) + return( rc ); =20 } ldap_pvt_thread_mutex_lock( &li->li_counter_mutex );