We have a three-server installation; one R/W, replicating to two R/O
instances. They are running 389-Directory/2.5.2
On the R/W instance, we are seeing a steady stream of errors of like:
ERR - NSMMReplicationPlugin - agmt="cn=S1" (az1:636): Schema
replication update failed: Constraint violation
ERR - NSMMReplicationPlugin - agmt="cn=S1" (az1:636): Warning: unable
to replicate schema: rc=1
for both replication targets (i.e. both S1 and S2)
I've exported, and examined, the replication change log. I don't see
anything in it I don't expect to see. It's full of normal, day-to-day
attribute adjustments.
I think the next step is enabling replication logging on a consumer. And
I think this is accomplished by adding 8,192 to the value in
nsslapd-errorlog-level of cn=config
On our test servers, I've found I can change this value by stopping the
instance and editing the dse.ldif Is there another way to do this which
does not require stopping and starting the instance?
--
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@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
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
