On Mon, Feb 17, 2025 at 10:58:08AM -0000, [email protected] wrote: > Hi, > Initially, all entries are present in both providers in a 2-node > multi-master setup. We export the data from node1 and import it into > node2 as part of the replication configuration, ensuring that both > nodes have identical data at the start. > > Most updates occur on node1, but there are scenarios where updates > also happen on node2. At some point, we observe that a glue value > appears.
Check your serverids are distinct and that your ACLs really allow full read access to the database for the replication identity, *especially* for this entry. If in doubt, try reading the entry with ldapsearch (using the replication identity). If you really can read it, you'll have to review the logs (enable loglevel sync) to check why it is being "removed" (turned into a glue entry). Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
