Join cluster to a group fails with no apparent errors when cluster name matches hostname or a part of FQDN
Originally Published: 2011-09-19
Article Number
Applies To
RSA Key Manager Appliance 2.7.x
Issue
When a join operation is invoked through RKM Appliance Operations Console (/rkmawa) => Operations tab => Cluster option, the web page shows some messages with a final line saying that a queue job has been made. There are no further messages or error indications on the cluster being joined to another group.
The primary node of the existing cluster (say ABC) to which the new cluster (say PROD) is being joined to, shows a message similar to the following in a log file /opt/rsa/cluster/logs/join_cluster.<date>.<hour>.log (even though the new cluster name PROD does not exist in /opt/rsa/cluster/master.cluster.info):
Cluster already exists. Not adding PROD.
Cause
Resolution
Notes
Related Articles
RSA Governance & Lifecycle Recipes: Dashboard - Deployment Overview - Part 2 Number of Views What about Profile Timeline in RSA Web Threat Detection, CProfileUpdater and Cassandra as part of version 6.1 upgrade? Number of Views Disable IPv6 on ethernet cards for audit compliance Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Deployment Overview - Part 1 Number of Views Generic REST Collector does not replace Query Parameters passed as part of the POST Request Body in RSA Identity Governanc… Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
