Hi There,

We are in the middle of implementing OpenLDAP into our network. We are testing 
our implementation and facing the below error in our logs after a node has 
either been powered off or the slapd service has been stopped (and subsequently 
brought back online):

syncprov_sendresp: 
cookie=rid=001,sid=001,csn=20200813144529.184309Z#000000#001#000000
do_syncrep2: rid=002 got search entry without Sync State control 
(dc=domain,dc=local)
do_syncrepl: rid=002 rc -1 retrying
syncprov_sendresp: 
cookie=rid=001,sid=001,csn=20200813144529.378496Z#000000#001#000000

This error is only encountered on the node that had been brought offline. Prior 
to this replication had/has been working without issue - as far as we can tell.

Below are the configuration LDIFs we used to enable replication:

dn: cn=config
changetype: modify
add: olcServerID
olcServerID: 1 ldap://ldap1.domain.local/
olcServerID: 2 ldap://ldap2.domain.local/

dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: syncprov.la

dn: olcOverlay=syncprov,olcDatabase={3}mdb,cn=config
objectClass: olcOverlayConfig
objectClass: olcSyncProvConfig
olcOverlay: syncprov

dn: olcDatabase={3}mdb,cn=config
changetype:modify
add: olcSyncrepl
olcSyncrepl: rid=001
  provider=ldap://ldap1.domain.local/
  binddn="cn=manager,dc=domain,dc=local"
  bindmethod=simple
  credentials=ldap_pw
  searchbase="dc=domain,dc=local"
  type=refreshAndPersist
  retry="5 5 300 +"
  timeout=1
olcSyncrepl: rid=002
  provider=ldap://ldap2.domain.local/
  binddn="cn=manager,dc=domain,dc=local"
  bindmethod=simple
  credentials=ldap_pw
  searchbase="dc=domain,dc=local"
  type=refreshAndPersist
  retry="5 5 300 +"
  timeout=1
-
add: olcMirrorMode
olcMirrorMode: TRUE

I have seen other posts about this error that mention the overlay not being 
properly configured, however, I don't think this is the case for us since 
replication does work as expected until a node is brought offline. 

It also seems that any changes made to online nodes are not replicated to the 
offline node when it is brought back online. However, any changes made after 
that node has been brought back online are replicated. I am sure this is 
probably a configuration issue but not sure where to go from here.

Any help is greatly appreciated.

Thanks!

Reply via email to