Thursday, February 29, 2024

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

there was an old RHEL-7.4 and RHEL-7.5 issue and fix in replication halt - pending list first CSN not committed, pending list increasing
but you have a (somehow) more recent version, 389-ds-base- ( and one 389-ds-base- ) , so this should be fixed.
the issue could have been related to sub operations.
the logs provided do show a replica with a large and growing pending list, taking several seconds to parse (in double digits).
and in this particular replication agreement, the consumer's max CSN is higher than the local supplier's one, so the remote replica/consumer is flagged as "ignored"
then later in time some updates go through as the RUV in the R.A. have been updated by a better knowledgeable replica.
but this seems to repeat (strange)
I want to suggest deleting the changelog, and re-init that replica, but maybe Thierry or Pierre or William B. have a better suggestion.

On Thu, Feb 29, 2024 at 2:21 PM William Faulk <> wrote:
> FYI: There is a list of pending operations to ensure that the RUV is not
> updated while an older operation is not yet completed. And I suspect that
> you hit a bug about this list. I remember that we fixed something in that
> area a few years ago ...

I think I found it, or something closely related.
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