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. 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 -- Kees _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
