[24/39]: creating DS keytab [25/39]: ignore time skew for initial replication [26/39]: setting up initial replication Starting replication, please wait until this has completed. Update in progress, 33 seconds elapsed [ldap://aws-b.ipa.example.com:389] reports: Update failed! Status: [Error (-2) connection error: Unknown connection error (-2) - Total update aborted]
[error] RuntimeError: Failed to start replication
and on the IPA Master server side directory server error log shows:
[05/Apr/2024:02:11:39.484729292 -0400] - WARN - NSMMReplicationPlugin - repl5_inc_run - agmt="cn=meToaws-a.ipa.example.com" (aws-a:389): The remote replica has a different database generation ID than the local database. You may have to reinitialize the remote replica, or the local replica.
When trying to install new replica it fails in replication stage. I have tried with different server as IPA server and also tried with a brand new serever which never existed before.
Replica fails in replication
Continue withiotu error
~]$ rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server package freeipa-server is not installed package freeipa-client is not installed ipa-server-4.9.6-10.module_el8.5.0+1055+c415bbe9.x86_64 ipa-client-4.9.6-10.module_el8.5.0+1055+c415bbe9.x86_64 389-ds-base-1.4.3.23-12.module_el8.5.0+1056+b3c5a4b9.x86_64 pki-ca-10.11.2-2.module_el8.5.0+945+a81e57da.noarch krb5-server-1.18.2-14.el8.x86_64
This cluster was installed long time ago and it was working. we noticed replication issue on the =ipaca for while, try to reinitialize the replication but it failed with the same database generation id error. however we can reinitialize replication for o=ipaca
Metadata Update from @frenaud: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Closing as duplicate of 9587