I am running sonarqube data center edition 8.9.1 in k8s, and in the app node, there is error about failure to connect to 44117, is that port needs to be open? Documentation on the purpose of that port?
Thanks
logs:
2021.07.07 16:38:30 INFO web[c.h.i.s.t.TcpServerConnector] [10.32.1.207]:33121 [SonarQube] [4.2] Connecting to /10.32.1.207:44117, timeout: 10000, bind-any: false
2021.07.07 16:38:30 INFO web[c.h.i.s.t.TcpServerConnector] [10.32.1.207]:33121 [SonarQube] [4.2] Could not connect to: /10.32.1.207:44117. Reason: SocketException[Connection refused to address /10.32.1.207:44117]
2021.07.07 16:38:30 INFO ce[c.h.i.i.NodeExtension] [10.32.1.207]:44117 [SonarQube] [4.2] Destroying node NodeExtension.
2021.07.07 16:38:30 INFO ce[c.h.i.impl.Node] [10.32.1.207]:44117 [SonarQube] [4.2] Hazelcast Shutdown is completed in 6002 ms.
2021.07.07 16:38:30 INFO ce[c.h.c.LifecycleService] [10.32.1.207]:44117 [SonarQube] [4.2] [10.32.1.207]:44117 is SHUTDOWN
Yes, that port needs to be open since it allows Hazelcast to perform cross-node communication (see Configure and operate a cluster):
Configuration details
There are three TCP networks to configure:
the network of application nodes that relies on Hazelcast.
the network used for Elasticsearch internal communication between search nodes ( es properties).
the network between application nodes and search nodes ( search properties).
Hazelcast is used to manage the communication between the cluster’s application nodes. You don’t need to install it yourself, it’s provided out of the box.
I don’t think you can use load balancers since we specify this description for sonar.cluster.hostshere:
Comma-delimited list of all application hosts in the cluster. This value must contain only application hosts .
You are welcome to try of course, but typically the load balancer will sit in front of SonarQube and Hazelcast will handle the “load balancing” of cross-node communication.
We are facing issue with Sonar while joining the cluster. We have specified the ports 9000 but it’s trying to connect dynamic ports and getting below error.
We have installed dour application with docker compose/
Can you please help me?
024.07.24 09:14:20 INFO sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnector] [10.185.56.141]:32975 [SonarQube] [5.2.1] Connecting to /10.185.48.85:44571, timeout: 10000, bind-any: false
2024.07.24 09:14:20 INFO sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnector] [10.185.56.141]:32975 [SonarQube] [5.2.1] Connecting to /10.185.48.85:39159, timeout: 10000, bind-any: false
2024.07.24 09:14:24 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.c.i.ClusterHeartbeatManager] [10.185.56.141]:32975 [SonarQube] [5.2.1] This node does not have a connection to Member [10.185.48.85]:44571 - 07c11b14-2a84-4a58-bc45-fd06e038b928
2024.07.24 09:14:24 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.c.i.ClusterHeartbeatManager] [10.185.56.141]:32975 [SonarQube] [5.2.1] This node does not have a connection to Member [10.185.48.85]:39159 - 0d4fe767-08b1-426b-9c01-86bd02b4219b
2024.07.24 09:14:29 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.c.i.ClusterHeartbeatManager] [10.185.56.141]:32975 [SonarQube] [5.2.1] This node does not have a connection to Member [10.185.48.85]:44571 - 07c11b14-2a84-4a58-bc45-fd06e038b928
2024.07.24 09:14:29 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.c.i.ClusterHeartbeatManager] [10.185.56.141]:32975 [SonarQube] [5.2.1] This node does not have a connection to Member [10.185.48.85]:39159 - 0d4fe767-08b1-426b-9c01-86bd02b4219b
2024.07.24 09:14:30 INFO sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnector] [10.185.56.141]:32975 [SonarQube] [5.2.1] Could not connect to: /10.185.48.85:44571. Reason: IOException[Connect timed out to address /10.185.48.85:44571]
2024.07.24 09:14:30 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnectionErrorHandler] [10.185.56.141]:32975 [SonarQube] [5.2.1] Removing connection to endpoint [10.185.48.85]:44571 Cause => java.io.IOException {Connect timed out to address /10.185.48.85:44571}, Error-Count: 8
2024.07.24 09:14:30 INFO sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnector] [10.185.56.141]:32975 [SonarQube] [5.2.1] Could not connect to: /10.185.48.85:39159. Reason: IOException[Connect timed out to address /10.185.48.85:39159]
2024.07.24 09:14:30 WARN sonarqube-9cca7eee-cb4e-4bd6-9c27-7e1a143a6be9 web[c.h.i.s.t.TcpServerConnectionErrorHandler] [10.185.56.141]:32975 [SonarQube] [5.2.1] Removing connection to endpoint [10.185.48.85]:39159 Cause => java.io.IOException {Connect timed out to address /10.185.48.85:39159}, Error-Count: 8