On 18-10-2021 16:30, Mark Reynolds wrote:
On 10/18/21 8:17 AM, Kees Bakker wrote:
> Hi,
>
> Today I tried 389-base 1.4.4.17 for a fix of retro cl trimming [1]
>
> Unfortunately the ns-slapd got into some sort of deadlock, I think.
> Anyway, I reverted 389-base back to 1.4.3.23.
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
/var/lib/dirsrc/slapd-INST/db/userroot/replication_changelog.db
Hmm. I don't
have these (files?).
I do have this directory: /var/lib/dirsrv/slapd-INST/db/changelog
Should I remove that whole directory?
Start the server, and reinit the agreements on this server
That should do it.
Mark
>
> But now I have a replication problem. Could this have been caused by
> the update to 1.4.4.17 ? 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
>
> [1]
https://github.com/389ds/389-ds-base/pull/4895
>
--
Directory Server Development Team