Replica synchronization is failing at "Downloading database from the primary" in RSA Authentication Manager 8.x
3 years ago
Originally Published: 2019-10-10
Article Number
000042470
Applies To
RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Issue
During the manual database sync between a primary and replica instance the synchronization fails at the step of Downloading database dump to replica .

Errors are found in the /opt/rsa/am/server/logs/replica_replication.log. In the example below, the mentioned sweep file in the error does not exist on the primary on the directory /opt/rsa/am/replication/p2r_sweeps_to_apply:
  
java.lang.RuntimeException: could not find sweep file /opt/rsa/am/replication/p2r_sweeps_to_apply/p2r_sweep_15325090.sql.gz 
with .sha256 file even though latest propagated sweep id is 15325090
at com.rsa.replication.ApplyP2R.isSweepFileReadyToBeApplied(ApplyP2R.java:313)
at com.rsa.replication.ApplyP2R.workIfNeccessary(ApplyP2R.java:71)
at com.rsa.replication.ReplicationRunnable.work(ReplicationRunnable.java:70)
at com.rsa.replication.util.ServiceCallable.work(ServiceCallable.java:110)
at com.rsa.replication.util.ServiceCallable.runMainLoopUnsafe(ServiceCallable.java:99)
at com.rsa.replication.util.ServiceCallable.runMainLoop(ServiceCallable.java:80)
at com.rsa.replication.util.ServiceCallable.call(ServiceCallable.java:42)
at com.rsa.replication.util.ServiceCallable.call(ServiceCallable.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:139)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
Cause
One or more of the files listed below might have been manually edited or removed from /opt/rsa/am/config/src/scripts on the primary server:
  • DBRefresh.groovy 
  • ReplicationUtils.groovy
These scripts are responsible for database synchronization and sweep file creation.
Resolution
To resolve this issue, clean copies of the *.groovy files listed must be restored to the Authentication Manager primary.

You can manually transfer the missing scripts from another primary server that is running the same version of RSA Authentication Manager and place them in /opt/rsa/am/config/src/scripts directory on the primary that shows the error. 

If you do not have a second primary, and are running RSA Authentication Manager 8.4 patch 5, copies of the files are attached to the article that can be used instead of pulling them from another primary server

The scripts for RSA Authentication Manager 8.4 patch 5 are attached to this article. If you are running a different version of the software, do not use these files. Contact RSA customer support to provide the correct scripts for your version.


 
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).

    Related Articles

    Trending Articles

    Don't see what you're looking for?