Internal replication error occurs after AM8.6 upgrades
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.6
Issue
(e.g.)
Cause
Resolution
Workaround
2. Check the replication, if it failed with the related to trusted root certificate (e.g. cert_RADIUS-Root-Cert.der), then login to the database on each REPLICA, run like this command:
delete from ims_certificates where name='cert_RADIUS-Root-Cert.der' and purpose ='RADIUS_TRUST_CERT' and ref_id ='NULL';
3. Then login to PRIMARY database, run this sql:
update RSA_REP.IMS_INSTANCE set deployed_state='out_of_sync' where is_primary='FALSE';
4. Then you should be able to synch the primary to replica in OC.
Notes
You can see the similar messages into ReplicaReplication.log.
| Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "uk_ims_certificates" Detail: Key (name, purpose, ref_id)=(cert_RADIUS-Root-Cert.der, RADIUS_TRUST_CERT, NULL) already exists. |
Related Articles
Replication Status 246Number of Views Replication Showing Internal Replication Error During Upgrade to RSA Authentication Manager 8.2 994Number of Views Check Replication Status 101Number of Views RSA Authentication Manager 8.x shows replication status as "Instance Offline" 2.99KNumber of Views RSA Authentication Manager 8.1 primary instance fails to upgrade to 8.2 with error: Replication flush failed 1.08KNumber of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?