Resolve Confluence Data Center Cluster Bootstrapping Error
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
Confluence node startup fails with "the cluster is running build XXXX of Confluence, while this node is running YYYY." The values for XXXX and YYYY refer to separate Confluence Build Numbers and will vary with your environment.
Error Log Detail
When attempting to start Confluence Data Center, you receive the following message in atlassian-confluence.log:
1
2
2017-05-31 21:04:28,952 ERROR [localhost-startStop-1] [atlassian.config.bootstrap.DefaultAtlassianBootstrapManager] init Home is not configured properly:
com.atlassian.config.ConfigurationException: Exception bootstrapping cluster:the cluster is running build XXXX of Confluence, while this node is running YYYYThis then leads to Confluence Data Center does not start due to Spring Framework error; as the configuration has not been completed. Despite the presence of the Spring Application Context error, this is not a permissions based problem - the root cause is the original configuration problem.
Fix the multicast address and version mismatch between nodes
A second node is using the same multicast IP address and is running a different version of Confluence. There are two possible scenarios where this error might occur:
A separate instance of a different version, that simply has the same multicast information as your original server
A different version of the same instance, connecting to the same database
If your two instances are separate (i.e, they have a different database) then simply adjusting the multicast address of one cluster to a different value will resolve the problem.
If there are multiple versions in the cluster (and they connect to the same database), look to see which is larger:
If the cluster is running the smaller build number, check the node that failed to start up (as described in Confluence won't start after upgrade because the build numbers don't match)
If the node is running the smaller build number, it suggests that the database has been upgraded by another node, and you should install the same version of Confluence
Verify the cluster settings in confluence.cfg.xml are valid for all nodes in the cluster, and all nodes are starting on the same version of Confluence. Ensure other instances of Confluence do not have the same cluster information. Then take down all nodes and restart them one at a time.
Contact Atlassian Support for further assistance with troubleshooting this error.
Was this helpful?