2.3. EKM server fails to start: “Node named x already exists in this cluster”

Engineering Knowledge Manager

EKM Troubleshooting Guide | Chapter 2: Installation and Setup Issues |

2.2. EKM server fails to start: “java.lang.OutOfMemoryError” |  | 2.4. Unable to Connect to an EKM Server When Running in Service Mode
Prev |  | Next

## 2.3. EKM server fails to start: “Node named `x` already exists in this cluster”

There is another EKM cluster node with the same cluster name and cluster node name on the same LAN. Recall from Naming the Cluster and Cluster Nodes that each EKM server on the same LAN must have a unique cluster name, and that each cluster node within a cluster must have a unique node name.

If there is another EKM cluster node with the same cluster name and cluster node name on the same LAN, EKM will fail to start, and will log an error message similar to the following:

    2015-10-29 17:34:39,577 ERROR [org.jboss.as.clustering.jgroups.MuxChannel]
    (MSC service thread 1-4) JGRP000016: exception in channelConnected()
    callback: java.lang.IllegalStateException: JBAS010272: A node named node1:node1
    already exists in this cluster. Perhaps there is already a server running
    on this host? If so, restart this server with a unique node name,
    via -Djboss.node.name=<node-name></node-name>

This issue can be resolved in either of the following ways:

Solution 1: Change the JGroups Multicast Configuration to configure the EKM server to use a multicast configuration that does not conflict with other EKM server(s) on the same LAN.

Solution 2: Change the EKM cluster name to a unique name as described in Appendix R: Changing the EKM Cluster Name.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.