Friday, March 1, 2024

[389-users] Re: Determining max CSN of running server

It's on a VM.

I don't have enough archived logs to show the progression of the serial number. However, I do have a text dump of the cldb, and I can filter it down to just the CSNs, and then to just the CSNs originated on this replica. The timestamp with the most CSNs is 752, and, of the 3323 unique timestamps, only 13 have more than 100 CSNs, only 267 have 10 or more, and 1299 are just a single change.

Here's the list, if you really want to look:

I can't come up with a rationale for the numbers, honestly. They should just start at zero for each unique timestamp, right?

> IIUC the consumer is currently catching up. Is the RUV, on the consumer, evolving ?

Based on the one set of debug logs, yes, but I'm not sure if that's an anomaly or not. I haven't been able to see it move since then, but I'm keeping an eye on it.

> Do you have fractional replication ?

Yes. This is actually part of an IdM/FreeIPA installation, so the regular things that are stripped out there:

nsds5ReplicaStripAttrs: modifiersName modifyTimestamp internalModifiersName internalModifyTimestamp
nsDS5ReplicatedAttributeList: (objectclass=*) $ EXCLUDE memberof idnssoaserial entryusn krblastsuccessfulauth krblastfailedauth krbloginfailedcount
nsDS5ReplicatedAttributeListTotal: (objectclass=*) $ EXCLUDE entryusn krblastsuccessfulauth krblastfailedauth krbloginfailedcount

William Faulk
389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

No comments:

Post a Comment