-
Bug
-
Resolution: Fixed
-
High
-
9.1.0, 9.1.1, 9.2.0, 9.2.2
-
26
-
Severity 2 - Major
-
121
-
Issue Summary
After upgrading Confluence 8.x multi node DC to 9.1 or 9.2, Synchrony of Confluence are unable to start up since hazelcast is prevented from running:
"Hazelcast CANNOT start on this node. No matching network interface found.\\nInterface matching must be either disabled or updated in the member configuration."
The previously configured ethernet interface worked without issue. This issue occurs within a Windows environment.
Steps to Reproduce
- In a Windows environment, install a multi-node Confluence 8.x Data Center Confluence instance
- You can run just one node but the setup must be multi-node, not non-clustered mode
- Confirm Synchrony is working as expected
- Upgrade Confluence to 9.1 or 9.2
Workaround
Manually updating the interface name in the confluence.cfg.xml via Hazelcast CANNOT start on this node. No matching network interface found..
*IMPORTANT*
If you applied this fix to fix Synchrony startup:
- Locate the synchrony-args.properties file in the <confluence-home-directory>
- Using admin privileges, edit the synchrony-args.properties file by adding the following parameters:
- Insert the following lines, replacing <IP> with the appropriate IP address of the server:
cluster.interfaces=<IP> synchrony.cluster.bind=<IP>
- Save the file
- Restart Confluence
it is highly recommended to un-do quoted fix if already applied as it doesn't fix problem completely for both Synchrony and Confluence.
To apply proper fix please follow steps as described in Hazelcast CANNOT start on this node. No matching network interface found