[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: RE : (ITS#6720) back-ldap core dump

Thank's for your time,

the write can't be stop, i have to reinstall all the replica , and my plann=
ing, for the second step, take 3 months ...



-----Message d'origine-----
De=A0: Pierangelo Masarati [mailto:masarati@aero.polimi.it]=20
Envoy=E9=A0: lundi 29 novembre 2010 15:21
=C0=A0: CHIROSSEL, Olivier
Cc=A0: openldap-its@openldap.org
Objet=A0: Re: RE : (ITS#6720) back-ldap core dump

olivier.chirossel@sfr.com wrote:

> Thank's for you reply,
> you can get a tar file containing a simple case which reproduce the probl=
>  here ( i don't put rewriting rules in proxy conf, just strip of  operati=
> nal  attribut )
> wget http://olivier:its6720@
> the lance.sh inititialise the tests=3D20
> (the slapd suppose to be in /usr/local/libexec)
> and you reproduce it with the command :
> ldapmodify -D "cn=3D3Dmanager,dc=3D3Dneuf,dc=3D3Dfr" -H "ldap://
:489"  -=3D
> w secret -f mod
> i try to explain you my need=3D20
> 1) For the moment i have a master in 2.3.x with many replica in 2.3.x wit=
h =3D
> slurpd replication
> 2) my goal is to migrate to a mirror mode master infrastructure with sync=
> pl replication
> 3) the first step is to install my mirror mode infrastructure and replica=
>  with slurpd from my old master.
> 4) second step re install replica one by one with syncrepl replication to=
> y new mirror mode infrastructure
> 5) third step write directly to my mirror mode infrastructure
> For the first step i put a proxy ldap between my old master and my mirror=
> ode infrastructure to do rewrite rules and strip operationnal attribut (i=
> eed, at the end,  have a new clean infrastructure with entryCSN contains =
> e ServerId of my new master, for checks the replcation status between my =
> ster and between my replica and my mirror mode architcture)
> =3D20
> The ldapmodify command reproduce the replication operations which highlig=
>   the problem..
> PS:=3DA0before strip attribute with rwm-map directives i try to put "last=
mod =3D
> off" in proxy ldap configuration without success ...

Thanks for the report.  I've reproduced the bug; it appears to be inside=20
slapo-rwm(5).  The core dump is related to a double free, which I'm=20
trying to track.

In any case, since as far as I understand the only reason you need=20
slapo-rwm(5) is to modify data during the migration, you should probably=20
do it offline, after exporting your data and before importing in the new=20