Ondřej, Still I don't quite understand: I had stopped the outdated node, deleted its accesslog, and restarted it, but still it would not sync. Then I stopped the updated node, removed the accesslog, then started it. Still the nodes would not sync. As the original node where tha data had been exported does not use delta syncrepl, I cannot import the accesslog database. So I wonder what I'll have to do to trigger a sync. To me it looks like some bug or even conceptual problem.
Currently the updated node logs nothing, while the outdated node periodically logs messages like: Mar 27 10:16:41 v06 slapd[30699]: do_syncrep1: rid=115 starting refresh (sending cookie=rid=115,sid=006,csn=20130719093756.074776Z#000000#000#000000;20250217105250.345944Z#000000#001#000000;20250218171739.629994Z#000000#002#000000;20250217065706.238392Z#000000#003#000000;20250227092327.859231Z#000000#005#000000;20250320153500.286773Z#000000#006#000000) Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=115 LDAP_RES_SEARCH_RESULT Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=115 LDAP_RES_SEARCH_RESULT (32) No such object Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=115 (32) No such object Mar 27 10:16:41 v06 slapd[30699]: do_syncrepl: rid=115 rc -101 retrying Mar 27 10:16:41 v06 slapd[30699]: do_syncrep1: rid=105 starting refresh (sending cookie=rid=105,sid=006,csn=20250320000000.000000Z#000000#000#000000;20250321000000.000000Z#000000#001#000000;20200721123717.002866Z#000000#002#000000;20181031083258.073732Z#000000#003#000000;20250325081318.563987Z#000000#005#000000;20250227092006.790591Z#000000#006#000000) Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=105 LDAP_RES_SEARCH_RESULT Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=105 LDAP_RES_SEARCH_RESULT (32) No such object Mar 27 10:16:41 v06 slapd[30699]: do_syncrep2: rid=105 (32) No such object Mar 27 10:16:41 v06 slapd[30699]: do_syncrepl: rid=105 rc -101 retrying Kind regards, Ulrich Windl > -----Original Message----- > From: Ondřej Kuzník <on...@mistotebe.net> > Sent: Tuesday, March 25, 2025 2:34 PM > To: Windl, Ulrich <u.wi...@ukr.de> > Cc: openldap-technical@openldap.org > Subject: [EXT] Re: accesslog with delta syncrepl: Why wouldn't contebnt be > synced? > > On Tue, Mar 25, 2025 at 09:25:38AM +0000, Windl, Ulrich wrote: > > Hi! > > > > I had just asked https://serverfault.com/q/1177576/407952, but I'll > > summarize here: > > I think I configured delta-syncrepl for a MMR correctly using OpenLDAP > > >= 2.5.18 (cn=config also synced). However when I offlined one node > > and updated the main DIT via slapadd, the other node wouldn't update > > its DIT when the offlined node is online again. > > Hi Ulrich, > nothing there indicates a replication issue, on the contrary. Not that > there's much information you've actually given, e.g. you mention > specific CSNs but they are missing in the logs you refer to, etc. > > > I wonder whether I have to empty or delete the corresponding > > accesslog, or is there some other step to perform? > > Yes, in deltasync the provider's accesslog is tightly linked to its main > DB, so any time you make offline changes to the main DB, you either wipe > accesslog (preferably) or restore it in lockstep. > > > Is delta syncrepl looking at the accesslog only to detect changes? > > It is replicating from it if it can: you can get conflicting writes in a > multi-writer environment which is when OpenLDAP has to fall back to > plain syncrepl to resolve them and then switches back to pulling them > from accesslog. > > Regards, > > -- > Ondřej Kuzník > Senior Software Engineer > Symas Corporation http://www.symas.com > Packaged, certified, and supported LDAP solutions powered by OpenLDAP
