Jira node fails to start with java.rmi.AccessException: Registry.rebind disallowed
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The second node of two node cluster does not start up and it fails with the following error
1
2
3
4
localhost-startStop-1 ERROR [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
net.sf.ehcache.CacheException: Problem starting listener for RMICachePeer //IT673438.HOSTS.CLOUD.ATLASSIAN.COM:40001/com.atlassian.jira.crowd.embedded.ofbiz.EagerOfBizUserCache.userCache. Initial cause was RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.rebind disallowed; origin /10.24.34.120 is non-local host
at com.atlassian.jira.cluster.distribution.localq.rmi.ehcache.RMICacheManagerPeerListener.notifyCacheAdded(RMICacheManagerPeerListener.java:543) Environment
Jira Data Center on any version from 8.0.0
Jira needs to be configured as a cluster of at least 2 nodes
Diagnosis
Compare the cluster.properties file in the home directory of each Jira node in the Jira Data Center cluster, and check if any parameter such as jira.node.id or ehcache.listener.hostName is duplicated across node. If that's the case, then this KB article is relevant.
Cause
Every node utilizes the IP address of local host for the RMI server to register its services. Having an IP address for the localhost that cannot be resolved to the localhost can cause the RMI server to not start up. This will cause the node startup process to fail.
Such parameter is configured on each Jira Data Center node in the cluster.properties file in their home directory with parameters (as explained in Set up a Jira Data Center cluster). While creating a new node, sometimes Jira admins might accidentally copy the cluster.properties file from a node to another node and forget to update the host address. This will cause the conflict between the localhost and the IP address provided under the ehcache.listener.hostName of the properties file, resulting in such an error and preventing the Jira node from starting up
Solution
Ensure that the cluster.properties file contains the IP address and other values specific only to the node where they are created or moved.
Was this helpful?