From jpayanides@prosodie.com Fri May 17 15:09:12 2019 From: jpayanides@prosodie.com To: openldap-bugs@openldap.org Subject: RE: (ITS#9023) crash using ppolicy chaining from slave to master Date: Fri, 17 May 2019 15:09:10 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2907317040333701859==" --===============2907317040333701859== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit --_000_AM0PR0202MB355359CC89C5DBD53D8FAB09BA0B0AM0PR0202MB3553_ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hello Quanah, I am not very familiar with gdb. Can you help me doing that? ________________________________ De : Quanah Gibson-Mount Envoy=E9 : vendredi 17 mai 2019 16:58:59 =C0 : AYANIDES, JEAN-PHILIPPE; openldap-its(a)OpenLDAP.org Objet : Re: (ITS#9023) crash using ppolicy chaining from slave to master --On Friday, May 17, 2019 3:50 PM +0000 jpayanides(a)prosodie.com wrote: > Full_Name: JPh Ayanides > Version: 2.4.47 > OS: Linux Debian > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.46.216.78) > > > Hello, I cannot succeed in making the following configuration to work. > Instead of that, openldap crashes. > > I have 2 openldap servers in master-slave: the slave is installed on a > machine named rada, and a master is installed on another machine named > simby. The ppolicy is activated on rada and simby, and I use chain and > updateref in order to sync failures in ppolicy coming from rada back to > simby. When I test that feature, with trying a bind with a wrong > password, openldap on the slave crashes. I failed in understanding why, > even with gdb. Ensure you have debugging symbols installed, and provide a full backtrace of all threads from gdb. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: This message contains information that may be privileged or confidential an= d is the property of the Capgemini Group. It is intended only for the perso= n to whom it is addressed. If you are not the intended recipient, you are n= ot authorized to read, print, retain, copy, disseminate, distribute, or use= this message or any part thereof. If you receive this message in error, pl= ease notify the sender immediately and delete all copies of this message. --_000_AM0PR0202MB355359CC89C5DBD53D8FAB09BA0B0AM0PR0202MB3553_ Content-Type: text/html; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

Hello Quanah,

I am not very familiar with gdb. = Can you help me doing that?

De : Quanah Gibson-Mount &l= t;quanah(a)symas.com>
Envoy=E9 : vendredi 17 mai 2019 16:58:59
=C0 : AYANIDES, JEAN-PHILIPPE; openldap-its(a)OpenLDAP.org
Objet : Re: (ITS#9023) crash using ppolicy chaining from slave to ma= ster
 
--On Friday, May 17, 2019 3:50 PM +0000 jpayan= ides(a)prosodie.com wrote:

> Full_Name: JPh Ayanides
> Version: 2.4.47
> OS: Linux Debian
> URL: ftp://ftp.openldap.o= rg/incoming/
> Submission from: (NULL) (195.46.216.78)
>
>
> Hello, I cannot succeed in making the following configuration to work.=
> Instead of that, openldap crashes.
>
> I have 2 openldap servers in master-slave: the slave is installed on a=
> machine named rada, and a master is installed on another machine named=
> simby. The ppolicy is activated on rada and simby, and I use chain and=
> updateref in order to sync failures in ppolicy coming from rada back t= o
> simby. When I test that feature, with trying a bind with a wrong
> password,  openldap on the slave crashes. I failed in understandi= ng why,
> even with gdb.

Ensure you have debugging symbols installed, and provide a full backtrace <= br> of all threads from gdb.

--Quanah


--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>

This message contains in= formation that may be privileged or confidential and is the property of the= Capgemini Group. It is intended only for the person to whom it is addresse= d. If you are not the intended recipient, you are not authorized to read, p= rint, retain, copy, disseminate, distribute, or use this message or any par= t thereof. If you receive this message in error, please notify the sender i= mmediately and delete all copies of this message. --_000_AM0PR0202MB355359CC89C5DBD53D8FAB09BA0B0AM0PR0202MB3553_-- --===============2907317040333701859==--