Only when the LDAP service is stopped:
With a manual edit of the dse.ldif configuration file after it is saved/duplicated.

Look and "carefully" select entries with definitions for
objectClass: nsds5replicationagreement
similar to for example
dn: cn=meTods2.example.test,cn=replica,cn=dc\3Dexample\2Cdc\3Dtest,cn=mapping tree,cn=config
and remove the corresponding paragraph.

Also review the entry similar to this example:
dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dtest,cn=mapping tree,cn=config
with a definition for
objectClass: nsds5replica
remove the nsState
or eventually remove the whole paragraph if not longer needed

Also review the paragraph with definition for
nsslapd-backend: xx
similar to this example
dn: cn=dc\3Dexample\2Cdc\3Dtest,cn=mapping tree,cn=config
nsslapd-backend: userRoot
nsslapd-state: backend
and review the  nsslapd-referral: attribute value

If there are more than 2 servers, the corresponding nsds50ruv would need to be cleaned up on the other systems.

it may be "easier" to run the DS console, and faster to create a new replica from "scratch" (that seem urgent if this now a single point of failure scenario)
and it may be interesting to collect a core file and stack trace if the version is current on the crashed system.

Thanks,
Marc S.

On Tue, Oct 15, 2019 at 12:49 PM I M <isabella.ghiurea@nrc-cnrc.gc.ca> wrote:
Hi All
we are facing some critical decisions, we have 2 server in multimaster replication , one of DS master is off-line/crashed
  how can we removed the replication agreement for  the online DS  master to the  off-line  DS master  ?

thank you
Isabella
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@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/389-users@lists.fedoraproject.org