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
Generic REST Collector does not replace Query Parameters passed as part of the POST Request Body in RSA Identity Governanc… Number of Views Embedded links in the body of Workflow Nodes that are defined with Job Level Variables as part of the link are not saved i… Number of Views Data purging fails with ORA-02292: integrity constraint (AVUSER.FK_xxxxxx violated - child record found) in RSA Identity G… Number of Views How to change the AveksaAdmin password in RSA Identity Governance & Lifecycle Number of Views RSA Governance & Lifecycle 8.0 Patch 07 HF01 Release Notes Number of Views
Trending Articles
Unable to login to RSA Authentication Manager Security Console as super admin Authentication Manager Administration Server with operations console service Fails to Start with "No config.xml Was Found"… Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update RSA Authentication Manager Upgrade Process RSA SecurID Software Token Distribution to Android from RSA Authentication Manager 8.1
Don't see what you're looking for?
