Confluence Crashed when start second node

razmik.baghdasaryan January 22, 2019

I am try to setup Confluence in DC mode on single machine
I use following docs
https://confluence.atlassian.com/doc/moving-to-confluence-data-center-203651.html\\ https://developer.atlassian.com/server/confluence/starting-a-confluence-cluster-on-a-single-machine/\\
After completed with one node Confluence is working fine,

but when I copy /opt/atlassian/confluence to /opt/atlassian/confluence2
and copy /home/confluence/confluence-data to /home/confluence/confluence-data-2

then I changed /opt/atlassian/confluence2/bin/setenv.sh and add this CATALINA_OPTS="-Dconfluence.cluster.hazelcast.listenPort=5851"
and also changed /opt/atlassian/confluence2/bin/conf/server.xml

<Connector port="9090" connectionTimeout="20000" redirectPort="9443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" proxyName="confluence.local" proxyPort="443" scheme="https" />

/*
/opt/atlassian/confluence2/ and also changed java_home path
*/

after that start first node and confluence started normally and after that start second node and first node was crashed but when I try with confluence.local:9090 it is working but confluence.local:8080 was crashed via https://confluence.local it is not disapled normally I send I logs what i see

Please see attachedurl for more logs  LOGS

this is a UI error:
message Could not open Hibernate Session for transaction; nested exception is com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!




1 answer

0 votes
Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 28, 2019

Hello Razmik,

Just so we ensure we understand, you’re attempting to run a single server with 2 nodes of Confluence Data Center within that single server.

With this said, running multiple nodes of Confluence Data Center on a single server removes some of the redundancy which you have when running Confluence Data Center on two servers with one node each. Running multiple nodes (more than 1) of Confluence Data Center on a single server will cause complications and errors, similar to what you’re experiencing here.

So we may understand the full scope of the goal here, what is your desired outcome with Confluence Data Center? Along with any requirements for running Data Center?

Additional documentation which may be helpful;

Installing Confluence Data Center

Confluence Data Center:  optimized for scale

Best practices for Atlassian Data Center  

Regards,
Stephen Sifers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events