On Thu, Jul 16, 2026 at 11:38:41AM -0700, Ben Poliakoff wrote:
> So it appears that perhaps I need to "fix" all of the entries with the
> older format of entryCSN.
> My quick "fix" that I've been doing when this issue comes up has been to:
>
> 1. create an ldif of the entry in question
> 2. delete the entry in question on the primary/provider slapd instance
> 3. re-create the entry on the primary/provider, using the ldif from step one
> 4. at this point subsequent changes to the entry are replicated promptly
> and without issue
>
> I don't love the idea of having to do this ~4k times, but can certainly do
> that if that's the best way forward. Is there any better/more efficient way
> to fix these entries with entryCSNs that are in the older format?

Hi Ben,
in order of (personal) preference:
- slapcat DB, filter out entryCSNs with that format, slapadd and then
  use that DB as the seed for the rest of the cluster
- do the above but transform the entryCSNs to the current format instead
  of removing them
- your suggestion
- downgrade to 2.6.10 and touch (an empty modify is ok) each of those
  entries, let it replicate then upgrade again

Regards,

--
Ondřej Kuzník
Senior Software Engineer
Symas Corporation                       http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP