eiamclustersetup to sync with primary gives "ERROR - Primary server <server>.<example>.<com> not present in failover list"

Products

• Autosys Workload Automation

Issue/Introduction

Customer tried to run eiamclustersetup -p <primary-server-name>  from a secondary EEM node, results in error below after picking current node and attempting a sync

 

Jun 04, 2025 4:45:29 PM IclUtil itechLibInit
INFO: iTechSDK initialized successfully
INFO  - EIAM_HOME [/opt/CA/SharedComponents/EmbeddedEntitlementsManager/]
INFO  - IGW_LOC [/opt/CA/SharedComponents/iTechnology/]
INFO  - DXHOME [/opt/CA/SharedComponents/CADirectory/dxserver/]
INFO  - Hostname identified as [<secondary>.<example>.<com>]
EiamAdmin password :
INFO  - Checking server status
INFO  - igateway status      [started]
INFO  - dxserver status      [started]
Are you sure you want to continue? [Y/N]:Y
[<secondary>.<example>.<com>]>list
-------------------------------------------------------
INFO  - Summary
=======================================================
INFO  - Listing failover nodes for server
-------------------------------------------------------
INFO  - Hostname:Dsa Port
-------------------------------------------------------
INFO  - <primary>.<example>.<com>(*):509
INFO  - <secondary>.<example>.<com>:509
-------------------------------------------------------
[<secondary>.<example>.<com>]>sync
=======================================================
INFO  - Select current machine hostname
=======================================================

..

..
ERROR - Primary server <primary-server-name>  not present in failover list
java.lang.Exception: Primary server <primary-server-name>  not present in failover list
        at com.ca.eiam.clustersetup.FailoverConfigurator.start<secondary>FailoverConfiguration(FailoverConfigurator.java:917)
        at com.ca.eiam.clustersetup.FailoverConfigurator.performAction(FailoverConfigurator.java:374)
        at com.ca.eiam.clustersetup.FailoverConfigurator.commandPrompt(FailoverConfigurator.java:350)
        at com.ca.eiam.clustersetup.FailoverConfigurator.main(FailoverConfigurator.java:107)
ERROR - Primary server <primary-server-name>  not present in failover list

 

Environment

AutoSys Workload Automation

Cause

eiam-clustersetup's -p  option value should be the same short hostname or a fully qualified server name, as what was used for primary server.

In the list output above, it shows both the server names there to be Fully Qualified names. The hostname string for the primary should match exactly the value for eiam-clustersetup's -p option.  

INFO  - Listing failover nodes for server
-------------------------------------------------------
INFO  - Hostname:Dsa Port
-------------------------------------------------------
INFO  - <primary>.<example>.<com>(*):509
INFO  - <secondary>.<example>.<com>:509
-------------------------------------------------------

 

Note: If short names are listed for primary above, then use short name for eiam-clustersetup -p value

 

 

Resolution

Use fully qualified name of the primary server for the -p option, example:

eiamclustersetup -p <primary>.<example>.<com>