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
eLearning Course: Authentication Manager 7.1 to 8.1.x Migration - Part 2 (15:54) Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Deployment Overview - Part 1 Number of Views eLearning Course: Authentication Manager 6.1 to 8.1.x Migration - Part 2 (33:26) Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Deployment Overview - Part 2 Number of Views eLearning Course: Authentication Manager 7.1 to 8.1.x Migration - Part 1 (13:14) Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
