--On Thursday, September 12, 2019 12:23 PM -0700 rammohan ganapavarapu rammohanganap@gmail.com wrote:

Quanah,

Thanks for quick response, i will consider your recommendations but i wanted to understand when does consumer go to REFRESH mode?

When it detects an inconsitency or error of some type.

5d7a6178 send_ldap_result: err=66 matched="" text="subordinate objects must be deleted first" 5d7a6178 syncrepl_del_nonpresent: rid=001 be_delete dc=example,dc=com (66) 5d7a6178 => bdb_entry_get: ndn: "dc=example,dc=com"

And here is the error. It would appear it's getting the deletes out of sequence as it was requested to delete a parent before a child.

I'd also note that back-bdb/hdb are deprecated.

I will re-iterate that you need to update to a current release. Anything else is just a waste of time. Please see the change log: https://www.openldap.org/software/release/changes.html

I'd also heavily advise using back-mdb with the current release and using delta-syncrepl.

I would also note that some overlays have undefined behavior in an MMR environment (such as ppolicy as documented in the slapo-ppolicy(5) man page). YMMV with such overlays in use.

--Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com