On 10/18/21 8:17 AM, Kees Bakker wrote:
> Today I tried 389-base 184.108.40.206 for a fix of retro cl trimming 
> Unfortunately the ns-slapd got into some sort of deadlock, I think.
> Anyway, I reverted 389-base back to 220.127.116.11.
Yeah the replication changelog was moved in 1.4.4, so by downgrading you
most likely corrupted the changelog. Stop the server, remove the old
changelog: /var/lib/dirsrv/slapd-INST/db/changelogdb, and the new one
Start the server, and reinit the agreements on this server
That should do it.
> But now I have a replication problem. Could this have been caused by
> the update to 18.104.22.168 ? And, if yes, how can I fix this?
> [18/Oct/2021:12:17:41.750334062 +0200] - ERR - NSMMReplicationPlugin -
> changelog program - _cl5AddThread - Invalid changelog state - 2
> [18/Oct/2021:12:17:41.782505596 +0200] - ERR - NSMMReplicationPlugin -
> send_updates - agmt="cn=iparep4.example.com-to-rotte.example.com"
> (rotte:389): Changelog database was in an incorrect state
> [18/Oct/2021:12:17:41.827732779 +0200] - ERR - NSMMReplicationPlugin -
> repl5_inc_run - agmt="cn=iparep4.example.com-to-rotte.example.com"
> (rotte:389): Incremental update failed and requires administrator action
>  https://github.com/389ds/389-ds-base/pull/4895
Directory Server Development Team
389-users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure