dsconf duplicate replica id

[Gary Waters]

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

[Marc Sauton]

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

Cordially,
Marc S.

On Mon, Apr 12, 2021 at 11:49 AM Gary Waters <gwaters-web(a)caltech.edu&gt;
wrote:

>  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(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.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://lists.fedoraproject.org/archives/list/[e-mail]...
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Gary Waters]

I think by just writing this email, I was able to think through my 
process, and figure out my issue. I havent been able to talk to anyone 
since working from home.

Thank you for being my outlet,

-Gary

On 4/12/21 11:43 AM, Gary Waters wrote:
> 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(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.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://lists.fedoraproject.org/archives/list/[e-mail]...
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Gary Waters]

I didnt see this while engrossed in my own mess, but I will add it to my 
notes!

Thanks so much,

-Gary

On 4/12/21 2:19 PM, Marc Sauton wrote:
>  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
>
>  Cordially,
>  Marc S.
>
>  On Mon, Apr 12, 2021 at 11:49 AM Gary Waters <gwaters-web(a)caltech.edu 
>  <mailto:[e-mail]>> wrote:
>
>      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(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      To unsubscribe send an email to
>      389-users-leave(a)lists.fedoraproject.org
>      <mailto:[e-mail]>
>      Fedora Code of Conduct:
>      https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>      <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>      List Guidelines:
>      https://fedoraproject.org/wiki/Mailing_list_guidelines
>      <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>      List Archives:
>      https://lists.fedoraproject.org/archives/list/[e-mail]...
>     
> <https://lists.fedoraproject.org/archives/list/[e-mail]...
>      Do not reply to spam on the list, report it:
>      https://pagure.io/fedora-infrastructure
>      <https://pagure.io/fedora-infrastructure>
>

[William Brown]

Always happy to help, and glad you solved it. 

PS: Work from home can be tough like that :( 

>  On 13 Apr 2021, at 09:08, Gary Waters <gwaters-web(a)caltech.edu&gt;
> wrote:
>  
>  I think by just writing this email, I was able to think through my process, and figure
> out my issue. I havent been able to talk to anyone since working from home.
>  
>  Thank you for being my outlet,
>  
>  -Gary
>  
>  On 4/12/21 11:43 AM, Gary Waters wrote:
> > 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(a)lists.fedoraproject.org
> > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.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://lists.fedoraproject.org/archives/list/[e-mail]...
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.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://lists.fedoraproject.org/archives/list/[e-mail]...
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia