On 6 Nov 2019, at 09:29, Oleg Cohen
<oleg.cohen(a)assurebridge.com> wrote:
Greetings,
I am running 389-DS cluster v1.4.0.13 on CentOS 7. I have two nodes at the moment with a
replication agreement set on both.
I have initialized replica on NODE2 from NODE1. A replication agreement started from
NODE2 to NODE1 and is now running non-stop for a number of hours. The number of changes
sent is large. Is there any way I can figure out what is happening and get to the bottom
of it? Not sure this behavior is normal.
Do you have an agreement from node 1 to node 2, and from node 2 to node 1? You need
agreements in both ways ...
I would appreciate any suggestions on how to resolve/remediate this situation.
Hmmm, I think you can try looking in the audit log to see what's being changed. Look
at /var/log/dirsrv/slapd-instance/audit.
You can also check the replication status by search the agreements as directory manager
under cn=config. There are some replication cli tools that may help too.
Replication does "wake up" and send changes frequently, so this is not
"unexpected" behaviour for replication to continue to run for a long time, even
if it's actually sending "nothing".
Does that help?
Thank you!
Oleg
_______________________________________________
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/389-users@lists.fedoraproje...
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs