Hello,
I have a strange problem, but maybe I have missed something.
I have two ldap servers openldap 2.5.7 in Multimaster delta-sync replication (copying the config from Quanah blog).
Recencly one of the two servers ran out of disk space, the one that recieve modifications. This server had an entry that had not been replicated on the second server.
After cleaning the disk, I restarted the server. I noticed in the log a lot of syncing activity. When the logs stopped to show activity : the contextCSN of both server are exactly the same (both context csn), but the entry has not been created on the second server.
What to do ?
Thanks in advance
--On Thursday, October 14, 2021 4:49 PM +0200 frederic.goudal@bordeaux-inp.fr wrote:
Hello,
I have a strange problem, but maybe I have missed something.
I have two ldap servers openldap 2.5.7 in Multimaster delta-sync replication (copying the config from Quanah blog).
Recencly one of the two servers ran out of disk space, the one that recieve modifications. This server had an entry that had not been replicated on the second server.
After cleaning the disk, I restarted the server. I noticed in the log a lot of syncing activity. When the logs stopped to show activity : the contextCSN of both server are exactly the same (both context csn), but the entry has not been created on the second server.
Do a modify of some sort on that entry on the server where it exists, that should force it to re-sync.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
frederic.goudal＠bordeaux-inp.fr -
Quanah Gibson-Mount