The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We had a working Confluence TST cluster with 2 nodes on version 7.13.0.
After updating both nodes to version 7.13.7 we have the following behavior:
When we then restart node 1, we have the same behavior (node 1 is ok but node 2 crashes with the same error).
So there seems to be a problem with the cluster after the update.
On both machines port 5801 is open on the firewall.
Errors:
confluencetst02 | 2022-06-15 08:43:04,086 INFO [Catalina-utility-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$5 Populating setup configuration if running with Cluster mode...
confluencetst02 | 2022-06-15 08:43:04,842 INFO [Catalina-utility-1] [confluence.cluster.hazelcast.HazelcastClusterManager] configure Configuring Hazelcast with instanceName [confluence], join configuration TCP/IP member addresses: 153.89.154.102|153.89.154.100, network interfaces [172.19.0.3] and local port 5801
confluencetst02 | 2022-06-15 08:43:04,842 INFO [Catalina-utility-1] [confluence.cluster.hazelcast.HazelcastClusterManager] startCluster Starting the cluster.
confluencetst02 | 2022-06-15 08:43:08,219 INFO [hz.confluence.event-2] [confluence.cluster.hazelcast.LoggingClusterMembershipListener] memberAdded [153.89.154.100]:5801 joined the cluster
confluencetst02 | 2022-06-15 08:43:08,221 INFO [hz.confluence.event-2] [confluence.cluster.hazelcast.LoggingClusterMembershipListener] logClusterMembers Cluster now has 1 members: [[153.89.154.100]:5801]
confluencetst02 | 2022-06-15 08:43:09,483 WARN [hz.confluence.cached.thread-2] [hazelcast.interceptor.authenticator.DefaultClusterJoinManager] checkNodeAuthenticationEnabled CONNECT(172.19.0.3:55333 -> 153.89.154.102:5801): Node authentication failed: Cluster authentication failed. Please make sure all members share the same value for 'confluence.cluster.name' and 'confluence.cluster.authentication.secret' in confluence.cfg.xml.
confluencetst02 | 2022-06-15 08:43:10,330 INFO [Catalina-utility-1] [confluence.cluster.hazelcast.HazelcastClusterManager] startCluster Confluence cluster node identifier is [91d9cc86]
confluencetst02 | 2022-06-15 08:43:10,330 INFO [Catalina-utility-1] [confluence.cluster.hazelcast.HazelcastClusterManager] startCluster Confluence cluster node name is [confluencetst02]
Any ideas?
The WARN that you are seeing is in reference to your confluence.cfg.xml in your home directory. It looks like the following two properties:
<property name="confluence.cluster.authentication.enabled">true</property>
<property name="confluence.cluster.authentication.secret">some_secret</property>
Verify that the secret is the same on both your servers. After making them the same for our servers, all nodes were able to join the cluster
Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.