Page created: 6 Nov 2019 |
Page updated: 25 Mar 2020
In this example, a naming conflict was encountered when the
replica attempted to replay an ADD of uid=user.200,ou=people,dc=example,dc=com.
In other words, two clients added the entry at the same time as an entry of the same name
was added on another replica.
[18/Feb/2010:14:53:12 -0600] category=EXTENSIONS severity=SEVERE_ERROR msgID=1880359005 msg="Administrative alert type=replication-unresolved-conflict id=bbd2cbaf-90a4-42af-94a8-c1a42df32fc6 class=com.unboundid.directory.server.replication.plugin.ReplicationDomain msg='An unresolved conflict was detected for DN uid=user.200,ou=People,dc=example,dc=com. The conflicting entry has been renamed to entryuuid=69807e3d-ab27-43a3-8759-ec0d8d6b3107+uid=user.200,ou=People,dc=example,dc=com'"
The Directory Server prepends the entryUUID to the
DN of the conflicting attribute and adds a
ds-sync-conflict-entryauxiliary object class to the entry to aid in search. For example, the following command searches for any entry that has the
ds-sync-conflict-entryobjectclass and returns only the DNs that match the filter. You should see the conflicting entry for uid=user.200.
$ bin/ldapsearch --baseDN dc=example,dc=com --searchScope sub \ "(objectclass=ds-sync-conflict-entry)" "1.1"
dn: entryuuid=69807e3d-ab27-43a3-8759-ec0d8d6b3107+uid=user.200,ou=People,dc=example,dc=com dn: entryuuid=523c430e-a870-4ebe-90f8-9cd811946420+uid=user.200,ou=People,dc=example,dc=comNote: Conflict entries are not returned unless the
objectclass=ds-sync-conflict-entryis present in the search filter.
After comparing the conflict entry with the target entry, the difference can be
applied in a manner similar to the previous example using ldapmodify
with the Replication Repair Control. The conflict entry can also be deleted
using this command. Run
bin/ldapmodify with the Replication Repair Control to
make the fix. When making changes using the Replication Repair Control, the
updates will not be propagated via replication. You should examine each and
every replica one by one, and apply the necessary modifications using the
$ bin/ldapmodify -J "18.104.22.168.4.1.3022.214.171.124" \ --filename difference.ldif