I'm experiencing this pretty regularly. srv-ds-2 will show messages of the following type:
``` [14/Dec/2024:15:29:58.343703946 -0600] - ERR - NSMMReplicationPlugin - changelog program - repl_plugin_name_cl - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): CSN 675de299000600140000 not found, we aren't as up to date, or we purged [14/Dec/2024:15:29:58.354587507 -0600] - ERR - NSMMReplicationPlugin - send_updates - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): Data required to update replica has been purged from the changelog. If the error persists the replica must be reinitialized. [14/Dec/2024:15:30:01.404036067 -0600] - ERR - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389) - clcache_load_buffer - Can't locate CSN 675de299000600140000 in the changelog (DB rc=-12797). If replication stops, the consumer may need to be reinitialized. ```
Both are on current Fedora 41 (specifically 389-ds-base 3.1.1-3 and freeipa-server 4.12.2-6) using lmdb databases (I just finished migrating this domain to lmdb, by deleting the previous ipa servers one at a time and rebuilding new ones in their place.) Is there a way to configure how long to keep the changelog? I can (and have) re-initialized ds-2 a couple of times at this point, but after the third time in as many days, it seems like I should look for other solutions than re-initialization.
Thanks!
On 2024-12-14 15:51, Martin Jackson via FreeIPA-users wrote:
I'm experiencing this pretty regularly. srv-ds-2 will show messages of the following type:
[14/Dec/2024:15:29:58.343703946 -0600] - ERR - NSMMReplicationPlugin - changelog program - repl_plugin_name_cl - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): CSN 675de299000600140000 not found, we aren't as up to date, or we purged [14/Dec/2024:15:29:58.354587507 -0600] - ERR - NSMMReplicationPlugin - send_updates - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): Data required to update replica has been purged from the changelog. If the error persists the replica must be reinitialized. [14/Dec/2024:15:30:01.404036067 -0600] - ERR - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389) - clcache_load_buffer - Can't locate CSN 675de299000600140000 in the changelog (DB rc=-12797). If replication stops, the consumer may need to be reinitialized.Both are on current Fedora 41 (specifically 389-ds-base 3.1.1-3 and freeipa-server 4.12.2-6) using lmdb databases (I just finished migrating this domain to lmdb, by deleting the previous ipa servers one at a time and rebuilding new ones in their place.) Is there a way to configure how long to keep the changelog? I can (and have) re-initialized ds-2 a couple of times at this point, but after the third time in as many days, it seems like I should look for other solutions than re-initialization.
Thanks!
I haven't seen any other comments, but I confirm the same log ERR on Fedora 41 between my two FreeIPA servers running 389-ds-base-3.1.1-3.fc41.x86_64 and freeipa-server-4.12.2-8.fc41.x86_64.
Hi,
On Sun, Feb 9, 2025 at 11:24 PM Anthony Messina via FreeIPA-users < freeipa-users@lists.fedorahosted.org> wrote:
On 2024-12-14 15:51, Martin Jackson via FreeIPA-users wrote:
I'm experiencing this pretty regularly. srv-ds-2 will show messages of the following type:
[14/Dec/2024:15:29:58.343703946 -0600] - ERR - NSMMReplicationPlugin - changelog program - repl_plugin_name_cl - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): CSN 675de299000600140000 not found, we aren't as up to date, or we purged [14/Dec/2024:15:29:58.354587507 -0600] - ERR - NSMMReplicationPlugin - send_updates - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389): Data required to update replica has been purged from the changelog. If the error persists the replica must be reinitialized. [14/Dec/2024:15:30:01.404036067 -0600] - ERR - agmt="cn=meTosrv-ds-1.imladris.lan" (srv-ds-1:389) - clcache_load_buffer - Can't locate CSN 675de299000600140000 in the changelog (DB rc=-12797). If replication stops, the consumer may need to be reinitialized.Both are on current Fedora 41 (specifically 389-ds-base 3.1.1-3 and freeipa-server 4.12.2-6) using lmdb databases (I just finished migrating this domain to lmdb, by deleting the previous ipa servers one at a time and rebuilding new ones in their place.) Is there a way to configure how long to keep the changelog? I can (and have) re-initialized ds-2 a couple of times at this point, but after the third time in as many days, it seems like I should look for other solutions than re-initialization.
Please have a look at https://docs.redhat.com/en/documentation/red_hat_directory_server/12/html-si...
flo
Thanks!
I haven't seen any other comments, but I confirm the same log ERR on Fedora 41 between my two FreeIPA servers running 389-ds-base-3.1.1-3.fc41.x86_64 and freeipa-server-4.12.2-8.fc41.x86_64.
-- _______________________________________________ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org 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.fedorahosted.org/archives/list/freeipa-users@lists.fedorahoste... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
freeipa-users@lists.fedorahosted.org