dsconf duplicate replica id

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey Everyone,

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 duplicate?

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 detected

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- repl-agmt \      create --suffix="ou=$suffix,o=school,c=us" --host=$consumer --port=389 \      --conn-protocol=StartTLS --bind-dn="cn=replication manager,cn=config" \
     --bind-passwd="x" --bind-method=SIMPLE --init \
     $agreement_name

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" --replica-id=$repid \
 --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,
Gary

Other info:
rhel8.3
389-ds-base-libs-1.4.3.17-1.module_el8+10764+2b5f8656.x86_64
389-ds-base-1.4.3.17-1.module_el8+10764+2b5f8656.x86_64
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux