Sample Header Ad - 728x90

OpenLDAP cluster: deletion of an entry is not replicated

1 vote
0 answers
59 views
We have an OpenLDAP 2.4 cluster of three nodes configured in multi-master and accessed through a VIP in round-robin. The three machines run RHEL7. We noticed that deletion of an entry (done from a Windows machine onto the first node via Oracle's tool ldapmodify.exe) is not replicated in the cluster i.e. the entry is not deleted from second and third node. Here's the relevant extract of cn=config for the first node: olcSyncrepl: {0}rid=001 provider=ldap://mynode2:389/ bindmethod=simple binddn="cn=Replicator,dc=mydomain,dc=org" credentials=1234567890 searchbase="dc=mydomain,dc=org" scope=sub schemachecking=on type=refreshAndPersist retry="30 5 300 +" keepalive="60:5:10" olcSyncrepl: {1}rid=002 provider=ldap://mynode3:389/ bindmethod=simple binddn="cn=Replicator,dc=mydomain,dc=org" credentials=1234567890 searchbase="dc=mydomain,dc=org" scope=sub schemachecking=on type=refreshAndPersist retry="30 5 300 +" keepalive="60:5:10" olcMirrorMode: TRUE Why does it happen and what could be done to fix this, apart from running ldapmodify on all three nodes (which we'd like to avoid)?
EDIT: After a few days we noticed that the cluster was in sync again. We looked up for the offending entry (thisentry) in all nodes' logs and we found this line on mynode3: Jun 18 14:18:20 mynode3 slapd: conn=1987936 op=14 DEL dn="dc=thisentry,ou=myou,ou=foobars,dc=mydomain,dc=org" There are no references to thisentry (apart from SRCH operations) on node1 and node2, even if the entry was originally deleted from node1, as said above.
Asked by dr_ (32068 rep)
Jun 14, 2019, 09:39 AM
Last activity: Jun 24, 2019, 12:42 PM