Hi,
We have a 4-machine setup with two providers (replicating between each other) and two consumers (for client access) that both replicate from both providers, type=refreshAndPersist
I'm trying to write a script to monitor replication, using the contextCSN attribute.
ldapsearch on the providers gives the expected the contextCSN attributes: contextCSN: 20230612115901.693614Z#000000#001#000000 contextCSN: 20230612115904.937471Z#000000#002#000000
However, the same ldapsearch on the consumers gives *no* contextCSN attributes *at all*. But when using slapcat to check directly on the consumers databases, we *can* see the attributes, and they are also up-to-date:
contextCSN: 20230612115801.572594Z#000000#001#000000 contextCSN: 20230612115804.594419Z#000000#002#000000
Is there any explanation, why I would be unable to obtain these contextCSN attributes through an ldapsearch?
This is RHEL7.9, with openldap 2.4.44
Thanks!
--On Monday, June 12, 2023 3:23 PM +0200 cYuSeDfZfb cYuSeDfZfb cyusedfzfb@gmail.com wrote:
Is there any explanation, why I would be unable to obtain these contextCSN attributes through an ldapsearch?
Do you have the syncprov overlay instantiated on the database on the consumers?
--Quanah
openldap-technical@openldap.org