I am running OpenLDAP 2.3.39 (locally built) on Red Hat Enterprise Linux
4 servers with several replicas. We use delta-syncrepl to keep the
replicas in sync with the master server.
We also use nagios and monitor the contextcsn value on the replica and
alert if it gets too far out of sync with the master server.
The issue we have now experienced a few times is that if there are a LOT
of updates in the nightly batch update process, that not all of the
updates make it to the replicas but the contextcsn stays in sync, so we
see strange errors that eventually lead us to see that the replicas are
not current even though they think they are.
Is this a known issue? I haven't found a syslog entry on the server or
the replicas that makes me think it is the flag of the root cause.
I have downloaded and built the 2.3.43 release, having installed it on
one replica. That replica is just as out of date this morning as the
others -- so, if there was a solution between 2.3.39 and 2.3.43 -- it
must have been on the provider side not the consumer side.
Thanks for any insight.
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)