Hi
Thank's for you reply,
you can get a tar file containing a simple case which reproduce the problem= here ( i don't put rewriting rules in proxy conf, just strip of operation= nal attribut )
wget http://olivier:its6720@84.103.237.12/its6720.tar
the lance.sh inititialise the tests=20 (the slapd suppose to be in /usr/local/libexec)
and you reproduce it with the command :
ldapmodify -D "cn=3Dmanager,dc=3Dneuf,dc=3Dfr" -H "ldap://127.0.0.1:489" -= w secret -f mod
i try to explain you my need=20
1) For the moment i have a master in 2.3.x with many replica in 2.3.x with = slurpd replication
2) my goal is to migrate to a mirror mode master infrastructure with syncre= pl replication
3) the first step is to install my mirror mode infrastructure and replicate= with slurpd from my old master.
4) second step re install replica one by one with syncrepl replication to m= 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 m= ode infrastructure to do rewrite rules and strip operationnal attribut (i n= eed, at the end, have a new clean infrastructure with entryCSN contains th= e ServerId of my new master, for checks the replcation status between my ma= ster and between my replica and my mirror mode architcture) =20 The ldapmodify command reproduce the replication operations which highlight= the problem..
PS:=A0before strip attribute with rwm-map directives i try to put "lastmod = off" in proxy ldap configuration without success ...
Regards,
Olivier
________________________________________ De : openldap-its@OpenLDAP.org [openldap-its@OpenLDAP.org] Date d'envoi : lundi 22 novembre 2010 17:43 =C0 : CHIROSSEL, Olivier Objet : Re: (ITS#6720) back-ldap core dump
*** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
Thanks for your report to the OpenLDAP Issue Tracking System. Your report has been assigned the tracking number ITS#6720.
One of our support engineers will look at your report in due course. Note that this may take some time because our support engineers are volunteers. They only work on OpenLDAP when they have spare time.
If you need to provide additional information in regards to your issue report, you may do so by replying to this message. Note that any mail sent to openldap-its@openldap.org with (ITS#6720) in the subject will automatically be attached to the issue report.
mailto:openldap-its@openldap.org?subject=3D(ITS#6720)
You may follow the progress of this report by loading the following URL in a web browser: http://www.OpenLDAP.org/its/index.cgi?findid=3D6720
Please remember to retain your issue tracking number (ITS#6720) on any further messages you send to us regarding this report. If you don't then you'll just waste our time and yours because we won't be able to properly track the report.
Please note that the Issue Tracking System is not intended to be used to seek help in the proper use of OpenLDAP Software. Such requests will be closed.
OpenLDAP Software is user supported. http://www.OpenLDAP.org/support/
-------------- Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.