--On Wednesday, March 3, 2021 6:24 PM +0100 Emmanuel Seyman
The problem is that I don't see any messages in the log that
out as being errors (granted, I'm not sure what I'm looking for).
In fact, the alert flaps every once in a while as the two nodes
come back in sync and drift away from each other again.
I find these values surprising considering I've never seen a syncrepl
error in the 2 years before the upgrade. Is there a known issue with
replication in 2.4.57 that would explain these sync differences?
The replication code in 2.4.44 was completely unreliable and could report
being in sync regardless of whether or not that was true. It's also
unknown to me if the nagios plugin is accurate for the current codebase.
Generally what you want to look at are the contextCSN values in the root of
the DIT of each server to see if they match. If you're using
delta-syncrepl, you need to also look at the contextCSN values in the root
of the accesslog DIT as well.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: