https://bugs.openldap.org/show_bug.cgi?id=10424
--- Comment #1 from Ondřej Kuzník <[email protected]> --- On Tue, Jan 13, 2026 at 01:37:24PM +0000, [email protected] wrote: > Trying to replicate cn=config but parially, I tried to set many syncrepl > directives so that each oe of them just replicate the single element it is > configured for. Here is an exemple thet replicate the frontend database and > only it: > [...] > > If I have this single syncrepl directive, all is ok, it replicates the > frontend > data and only this entry. > > Would I like to replicate, says, 'cn=config' with another syncrepl directive > like: > [...] > > where the search base is different, then suddenly I get some 'CSN too old' > errors, which make totally sense as we only have one single contextCSN stored > in the root entry (cn=config in my use case). > > I know I'm really border line here (and the rational is that I want a partial > replication of cn=config because the two servers are a bit different), but I > would suggest that the contextCSN to be stored in the entry associated to the > searchBase, not at the root of the database. Hi Emmanuel, yes, this is currently not supported, each DB is expected to only have one consumer (searchbase post suffixmassage) set up taking full ownership of that subtree. That's it and changing it would probably be a bigger piece of work, potentially blocked on splitting syncrepl into its own overlay which hasn't really happened yet. Regards, -- You are receiving this mail because: You are on the CC list for the issue.
