000016674 - Replica attachment fails in Authentication Manager 8.0 with an error

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000016674
Applies ToRSA Authentication Manager 8.0
AM 8.1
IssueReplica attachment fails in Authentication Manager 8.0 with an error
Operations console progress screen display error to delete replica and start over

appliance_setuplogs\radius\sbrsetuptool.log


INFO: SBR Radius services directory is /opt/rsa/am/radius/


WARNING: Failed to resolve FQDN: res = -1 1


appliance_setuplogs\quick_setup\logs\imsConsoleTrace.log


@@@2013-06-04 14:50:24,720, [AddReplica], (AttachReplicaThread.java:137), trace.com.rsa.amappliance.web.quicksetup.replicaattach.AttachReplicaThread, ERROR, <FQDN blacked out> ,,,,Failed to attach. Primary host: <FQDN blacked out>,,,,, exception:


com.rsa.amappliance.web.quicksetup.util.SetupException: Execution of config goal Appliance:configureReplica failed with exit code 1


appliance_setuplogs\quick_setup\logs\rsa-console.log


@@@2013-06-04 14:47:15,302 ERROR [AddReplica] GUILog.traceThrowable(637) | error:


com.rsa.amappliance.web.quicksetup.util.SetupException: Execution of config goal Appliance:configureReplica failed with exit code 1


 

appliance_setuplogs\install_logs\config\config.sh_Appliance_configureReplica_<DATE>.log


538022 2013-06-04 13:23:48,165 FATAL: Error enabling replication for SBR server <FQDN blacked out>'


538045 2013-06-04 13:23:48,188 FATAL:


Error enabling replication for SBR server <FQDN blacked out>'


java.lang.AssertionError: Error enabling replication for SBR server <FQDN blacked out>'
---------------------------config.sh_Appliance_configureReplica_<date_time>.log------------
FATAL: Did not receive the first change from the primary within the expected time period

CauseWhile most of the components of Authentication Manager can utilize both DNS as well as the hosts file, SBR RADIUS relies solely on DNS.  In this case, the hosts files were correct but there was an incorrect DNS entry somewhere in the network.  This caused RADIUS to be unable to resolve the FQDN which caused the replica attachment to fail.
ResolutionFix the entries in DNS and then flush all DNS caches and ARP tables.  Alternatively, reinstall the server with a new name and create new DNS entries with the correct information.  Then try the replica attachment process again.
Legacy Article IDa61626

Attachments

    Outcomes