Synchrony not starting on Docker or Kubernetes Data Center

[Chris Mooney]

Hi all,

We're having issues getting Synchrony started in the latest version of Confluence Data Center in Docker locally on my machine and in Kubernetes.

We receive the error "Hazelcast CANNOT start on this node. No matching network interface found.\nInterface matching must be either disabled or updated in the hazelcast.xml config file."

If I look at the confluence.cfg.xml this system property doesn't exist:

<property name="confluence.cluster.interface">eth0</property>

I've tried adding this property in the confluence.cfg.xml file but this does not fix the issue. I've also added confluence.cluster.interface=eth0 to my synchrony-args.properties file in my shared home directory. If I look at the atlassian-confluence.log I see: 

[plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment /opt/java/openjdk/bin/java -classpath /opt/atlassian/confluence/temp/4.0.0-master-85ceb9cf.jar:/opt/atlassian/confluence/confluence/WEB-INF/lib/postgresql-42.2.8.jar -Xss2048k -Xmx1g -Dconfluence.cluster.interface=eth0 synchrony.core sql 

However, this still doesn't fix the issue.

Is there a fix for this issue? Has anyone been able to get Synchrony started in Data Center?

[Corey Dyson]

Hey Chris,

Were you able to resolve this issue? I'm having the same problem.