Is there a way reliable determine whether ldap slave is sync with master? Currently i am using ContextCSN diff between master and slave to determine the lag.Thanks in advance.
AshokOn Fri, Jul 12, 2013 at 9:26 PM, Quanah Gibson-Mount <email@example.com> wrote:
It sounds like it is resyncing the DB, and skipping entries that already exist: LDAP_ALREADY_EXISTS is error code 68.--On Friday, July 12, 2013 5:40 PM +0530 Ashok <firstname.lastname@example.org> wrote:
I am running ldap master and multiple slave with RefreshandPersist config.
ldap search for an user shows different set of records. ContextCSN on
master and slave are exactly same.
What can i do to fix this. I tried restarting slave ldap but didn't help.
Also i keep getting do_syncrepl: rid=112 rc 68 retrying every minute. I
doubt if there is replication issue.
Sr. Member of Technical Staff
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration