you can either run a "dsconf replication get-ruv" like tis example:
dsconf -j ldapi://%2fvar%2frun%2fslapd-m1.socket replication get-ruv --suffix=dc=example,dc=test
or an ldapsearch to get the RUV records, similar to this example:ldapsearch -o ldif-wrap=no -LLLH ldaps://m1.example.test:636 -D "cn=directory manager" -W -b dc=example,dc=test "(&(nsUniqueId=ffffffff-ffffffff-ffffffff-ffffffff)(objectClass=nstombstone))" nsds50ruv
or review the dse.ldif configuration file, and search for a replication agreement definition ( objectClass: nsds5replicationagreement ), and locate the attributes nsds50ruv, DN example:
dn: cn=m1tom2exampleSSL,cn=replica,cn=dc\3Dexample\2Cdc\3Dtest,cn=mapping tree,cn=config
On Mon, Apr 12, 2021 at 11:49 AM Gary Waters <firstname.lastname@example.org> wrote:
I love the new dsconf python tool. Its great, and big upgrade over the
perl scripts that I think I have been using for decades.
However I am having a problem using it when making new replication
agreements between multiple masters.
How do I find the duplicates and how do i run dsconf to avoid that
Error after agreements are made:
Error (11) Replication error acquiring replica: Unable to acquire
replica: the replica has the same Replica ID as this one. Replication is
aborting. (duplicate replica ID detected)
Error (11) Replication error acquiring replica: duplicate replica ID
I know how to delete the newly made agreements no problem, but how do I
recreate them to avoid the duplicates? when creating the agreements I
didnt see a way to set an id.
command for the individual agreement.. maybe I am doing something wrong.
This is how I setup the agreement:
dsconf -D "cn=Directory Manager" -w $pass ldap://$supplier-
create --suffix="ou=$suffix,o=school,c=us" --host=$consumer
--bind-passwd="x" --bind-method=SIMPLE --init \
And this is how I setup the id and replication for the for the suffix:
dsconf -D "cn=Directory Manager" -w $pass ldap://$consumer replication \
enable --suffix="ou=$suffix,o=school,c=us" --role="master"
--bind-dn="cn=replication manager,cn=config" --bind-passwd=XXX
In my case I have 3 masters that I need to setup MMR between, and this
error happens when I added the third. It says replication is already set
for the suffix as mmr, which is correct, but I cant set a new repid for
each aggreement via the first command.
Thank you everyone,
389-users mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure