Required property 'buildHash' error when joining a Bitbucket Server node to a cluster
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
Problem
When trying to start a Bitbucket Server node the following appears in the atlassian-bitbucket.log of the node failing to start:
1
com.atlassian.stash.internal.cluster.NodePassivationException: The current node has been passivatedAnd the following appears in the atlassian-bitbucket.log of a node already joined in the cluster:
1
2
3
4
5
6
7
8
9
10
11
com.atlassian.stash.internal.cluster.NodeConnectionException: Required property 'buildHash' should be '96ae4b5935a56118586e500ee6f9433f09fe1903' but is 'ca3ded23381850df9c34637fb9ee88687abe43e0'
at com.atlassian.stash.internal.cluster.DefaultClusterJoinManager.negotiateOutcome(DefaultClusterJoinManager.java:262)
at com.atlassian.stash.internal.cluster.DefaultClusterJoinManager.accept(DefaultClusterJoinManager.java:95)
at com.atlassian.stash.internal.hazelcast.ClusterJoinSocketInterceptor.onAccept(ClusterJoinSocketInterceptor.java:46)
at com.hazelcast.nio.tcp.TcpIpConnectionManager.interceptSocket(TcpIpConnectionManager.java:176)
at com.hazelcast.nio.tcp.SocketAcceptorThread.configureAndAssignSocket(SocketAcceptorThread.java:240)
at com.hazelcast.nio.tcp.SocketAcceptorThread.acceptSocket(SocketAcceptorThread.java:225)
at com.hazelcast.nio.tcp.SocketAcceptorThread.handleSelectionKeys(SocketAcceptorThread.java:173)
at com.hazelcast.nio.tcp.SocketAcceptorThread.acceptLoop(SocketAcceptorThread.java:125)
at com.hazelcast.nio.tcp.SocketAcceptorThread.run(SocketAcceptorThread.java:103)
... 20 frames trimmedCause
The version of Bitbucket Server running on the node differs from the version of Bitbucket Server in the cluster. This can be due to attempting a rolling upgrade. Rolling upgrades are not supported as mentioned in our FAQ: Can Bitbucket Data Center be upgraded without downtime (i.e., a rolling upgrade)?
Resolution
Ensure that all nodes are running the same version. If they have just been upgraded and are all running the correct version, then perform complete staggered reboot of the cluster to ensure the cluster is up-to-date. You can find instructions on how to upgrade your server at Bitbucket Server Upgrade Guide
Was this helpful?