HI Quanah,

Yes, there was duplicate values in DIT which was causing slaves to not sync the data.

Thanks for your guidance

Regards,
Aravind M D

On Sun, Nov 18, 2018 at 3:35 AM Quanah Gibson-Mount <quanah@symas.com> wrote:
--On Saturday, November 17, 2018 9:38 PM +0530 aRaviNd
<ambadiaravind@gmail.com> wrote:

> If remove the schema changes replication works fine. Could you please let
> us know whats going wrong with the configuration?

Most likely, you have two values in the attribute that are different when
case sensitive, but the same when case insensitive, i.e.:

memberUID: AbcD
memberUID: aBCd

Before your schema change, these are considered different.  AAfter your
schema change, they are the same.  So when a modification occurs to the
attribute they are now seen as duplicate values and it breaks replication.

--Quanah



--

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