000017551 - Can't Attach RSA Authentication Manager 8.1 replica when Primary has migrated data.

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 Number000017551
Applies ToRSA Authentication Manager version 8.1, AM 8.1, AM 8.0, AM 8.x, migration, migrated data, replica attachment fails.
 
IssueConfiguration step Appliance:configureReplica [FAILED] at end of config.sh_Appliance_configureReplica_<date>.log
End/bottom of the appliance_setuplogs\install_logs\config\ config.sh_Appliance_configureReplica_<date>.log
...138716 2014-06-05 10:49:46,182 INFO: Executing /opt/rsa/am/pgsql/bin/psql
139260 2014-06-05 10:49:46,726 INFO: return code for sql script 0
142488 2014-06-05 10:49:49,954 INFO: Executing pg_restore.  Log output will be found here: /opt/rsa/am/install_logs/dbscripts/pg_restore-20140605104949.log
142490 2014-06-05 10:49:49,956 INFO: Executing /opt/rsa/am/pgsql/bin/pg_restore
Exception in thread "Main Thread" : exec returned: 1
    at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:646)
    at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:672)
    at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:498)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at Utils.exec(Utils.groovy:326)
    at Utils$exec$0.call(Unknown Source)
    at SetupReplica.loadPrimaryDatabase(SetupReplica.groovy:233)
    at SetupReplica.configureReplicaDatabaseAndPrepareForReplication(SetupReplica.groovy:385)
    at SetupReplica.configureReplica(SetupReplica.groovy:65)
    at SetupReplica$configureReplica.call(Unknown Source)
    at Appliance.configureReplica(Appliance.groovy:29)
    at com.rsa.plugins.install.GroovyInstallEngine.invokeScript(GroovyInstallEngine.groovy:68)
    at com.rsa.plugins.install.GroovyInstallEngine$_runTask_closure2.doCall(GroovyInstallEngine.groovy:57)
    at com.rsa.plugins.install.GroovyInstallEngine.runTask(GroovyInstallEngine.groovy:60)
    at com.rsa.plugins.install.GroovyInstallEngine$_runTasks_closure3.doCall(GroovyInstallEngine.groovy:106)
    at com.rsa.plugins.install.GroovyInstallEngine.runTasks(GroovyInstallEngine.groovy:105)
    at com.rsa.plugins.install.GroovyInstallEngine$runTasks.call(Unknown Source)
    at com.rsa.plugins.install.CommandLineInstallEngine.main(CommandLineInstallEngine.groovy:40)
Configuration step Appliance:configureReplica [FAILED]
2014-06-05 10:49:15,084 WARN: Bootstrap secret SUPERUSER_PASSWORD not available, temporary falling back on dev secrets 107677 config.sh_Appliance_configureReplica_<date>.log
[touch] Creating /opt/rsa/am/quick_setup/ready-for-attach
Configuration step InstallAM:installReplicaAfterQuickSetup [SUCCESS]
in the Replica's appliance_setuplogs/install_logs/config/config.sh_InstallAM_installReplicaAfterQuickSetup_<date>.log
INFO: Skipping update postgres memory_tuned_params.conf since AM is not deployed yet9876
[exec] net.ipv4.conf.default.promote_secondaries = 1
[exec] kernel.shmall = 2058465
Configuration step InstallAM:updateMemoryTuning [SUCCESS]
in the appliance_setuplogs\install_logs\config\InstallAM_updateMemoryTuning.log
CauseMigrated database contained the agent host entry for the replica from when it was attached to the AM 7.1 Primary.  Same replica name was used, so database cannot create a new agent host entry for the AM 8.1 replica because the AM 7.1 replica was in the database during the migration utility run.
 
Resolution

Either Name resolution or Same replica name in migrated Database from old Replica;


1.        The replica, pdcaceqr, cannot adequately resolve the Primary, . or


2.       The database still has an authentication agent host entry for the replica pdcaceqr in it, from migration.


For #1 check the /etc/hosts file on the replica, and add the following line


                <Primary_IP>         <Primary_FQDN>    <Primary_ShortName>


There should already be a replica entry


                <replica_IP>         <Replica_FQDN>    <Replica_ShortName>


For #2, go to Primary and look in Access ? Authentication Agents ? Manage Existing. 


And delete any entry for replica.

Legacy Article IDa66594

Attachments

    Outcomes