One of node in Bitbucket Data Center cluster is not coming up after restart with no error in logs.
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 Bitbucket Data Center node is not joining the cluster with the existing operational Bitbucket node and is generating a warning message, "Clustering is not enabled," in the logs.
Entry in the atlassian-bitbucket.log:
1
2
3
4
5
2024-07-30 11:33:51,732 WARN.[spring-startup]com.hazelcast.instance.Node [10.x.x.x]:5701 [devops] [1.2.3] No join method is enabled! Starting standalone
2024-07-30 11:18:35,267 WARN [hz.hazelcast.cached.thread-1]com.hazelcast.nio.tcp.TcpIpAcceptor.internal.cluster.NodeConnectionException: Clustering is not enabled
com.atlassian.stash.internal.cluster.NodeConnectionException: Clustering is not enabled
[10.x.x.x:5701 [dev] [1.2.3]com.atlassian.stashEnvironment
Tested in Bitbucket Data Center 8.9.16
Applied to Bitbucket Data Center 8.x
Diagnosis
Verify the following commands between both nodes:
a. ping <hostname>
b. telnet <hostname> <port>
Verify if the NFS mount point is defined correctly or not in /etc/fstab file on the Bitbucket Server.
Verify the content inside the <Bitbucket_Home>/shared directory if the directory and files are present or missing.
Cause
This behavior typically occurs when the mount -a command is executed to mount the shared path to the NFS server, and the command completes without error; however, the shared path is not properly mounted on the Bitbucket server or node. In this scenario, the entry in the /etc/fstab file contains the correct information, and network commands such as ping and telnet function correctly between the nodes. Nonetheless, attempting to unmount the shared directory path specified in /etc/fstab using the command unmount <shared directory path> may indicate that the path is not mounted.
Therefore, the user should execute the mount command with the specific shared directory path, rather than using the mount -a command.
1
2
3
Earlier Command -> mount -a
New Command -> mount <Bitbucket_shared_directory_path> Solution
To resolve this issue, mount the Bitbucket shared directory specified in the /etc/fstab file by using the mount <Bitbucket_shared_directory> command, instead of the mount -a command.
Was this helpful?