Sonarqube-dce 10.3.0 version failed to install on kubernetes

Must-share information (formatted with Markdown):

2024.01.17 21:34:25 WARN  sonarqube-dce-sonarqube-dce-app-7d75448c9b-swkrl app[][c.h.cp.CPSubsystem] [10.131.2.95]:9003 [SonarQube] [5.3.2] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
2024.01.17 21:34:27 INFO  sonarqube-dce-sonarqube-dce-app-7d75448c9b-swkrl app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.01.17 21:34:28 ERROR sonarqube-dce-sonarqube-dce-app-7d75448c9b-swkrl app[][o.s.application.App] Startup failure
org.elasticsearch.ElasticsearchException: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at org.elasticsearch.client.RestHighLevelClient.performClientRequest(RestHighLevelClient.java:2695)
	at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:2171)
	at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:2137)
	at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:2105)
	at org.elasticsearch.client.ClusterClient.health(ClusterClient.java:151)
	at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:79)
	at org.sonar.application.cluster.ClusterAppStateImpl.isElasticSearchOperational(ClusterAppStateImpl.java:209)
	at org.sonar.application.cluster.ClusterAppStateImpl.isOperational(ClusterAppStateImpl.java:106)
	at org.sonar.application.SchedulerImpl.isEsOperational(SchedulerImpl.java:180)
	at org.sonar.application.SchedulerImpl.tryToStartWeb(SchedulerImpl.java:151)
	at org.sonar.application.SchedulerImpl.tryToStartAll(SchedulerImpl.java:135)
	at org.sonar.application.SchedulerImpl.schedule(SchedulerImpl.java:113)
	at org.sonar.application.App.start(App.java:59)
	at org.sonar.application.App.main(App.java:81)
Caused by: java.util.concurrent.ExecutionException: java.net.ConnectException: Connection refused
	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:257)
	at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:244)
	at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:75)
	at org.elasticsearch.client.RestHighLevelClient.performClientRequest(RestHighLevelClient.java:2692)
	... 13 common frames omitted
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
	at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:174)
	at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:148)
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351)
	at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221)
	at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
	at java.base/java.lang.Thread.run(Unknown Source)

elastic search also failed to start

2024.01.17 21:38:38 INFO  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.t.TransportService] publish_address {10.131.3.249:9002}, bound_addresses {10.131.3.249:9002}
2024.01.17 21:38:39 INFO  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.b.BootstrapChecks] bound or publishing to a non-loopback address, enforcing bootstrap checks
2024.01.17 21:38:39 INFO  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterBootstrapService] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2]
2024.01.17 21:38:49 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2] to bootstrap a cluster: have discovered [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [10.131.1.56:9002, 10.131.1.97:9002] from hosts providers and [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
2024.01.17 21:38:59 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2] to bootstrap a cluster: have discovered [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [10.131.1.56:9002, 10.131.1.97:9002] from hosts providers and [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
2024.01.17 21:39:09 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2] to bootstrap a cluster: have discovered [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [10.131.1.56:9002, 10.131.1.97:9002] from hosts providers and [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
2024.01.17 21:39:19 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2] to bootstrap a cluster: have discovered [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [10.131.1.56:9002, 10.131.1.97:9002] from hosts providers and [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
2024.01.17 21:39:29 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [sonarqube-dce-sonarqube-dce-search-0, sonarqube-dce-sonarqube-dce-search-1, sonarqube-dce-sonarqube-dce-search-2] to bootstrap a cluster: have discovered [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [10.131.1.56:9002, 10.131.1.97:9002] from hosts providers and [{sonarqube-dce-sonarqube-dce-search-0}{EAaVHINWSKG2DAWXLabjNA}{3cHaXqxZSGaiCpEZPAEPuw}{sonarqube-dce-sonarqube-dce-search-0}{10.131.3.249}{10.131.3.249:9002}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see https://www.elastic.co/guide/en/elasticsearch/reference/8.11/discovery-troubleshooting.html
2024.01.17 21:39:39 WARN  sonarqube-dce-sonarqube-dce-search-0 es[][o.e.c.c.ClusterFormationFailureHelper] master not discovered yet, this node

Caused by: org.sonar.api.utils.MessageException: Database collation must be case-sensitive and accent-sensitive. It is SQL_Latin1_General_CP1_CI_AS but should be SQL_Latin1_General_CP1_CS_AS.

2024.01.17 23:54:44 WARN  sonarqube-dce-sonarqube-dce-app-56758bd774-lx8lt app[][c.h.cp.CPSubsystem] [10.131.1.18]:9003 [SonarQube] [5.3.2] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
2024.01.17 23:54:50 INFO  sonarqube-dce-sonarqube-dce-app-56758bd774-lx8lt app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.01.17 23:54:52 ERROR sonarqube-dce-sonarqube-dce-app-56758bd774-lx8lt app[][o.s.a.SchedulerImpl] Initialization failed. All nodes must be restarted
2024.01.17 23:54:18 WARN  sonarqube-dce-sonarqube-dce-app-56758bd774-4v66h app[][c.h.cp.CPSubsystem] [10.131.2.95]:9003 [SonarQube] [5.3.2] CP Subsystem is not enabled. CP data structures will operate in UNSAFE mode! Please note that UNSAFE mode will not provide strong consistency guarantees.
2024.01.17 23:54:34 INFO  sonarqube-dce-sonarqube-dce-app-56758bd774-4v66h app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.01.17 23:54:35 INFO  sonarqube-dce-sonarqube-dce-app-56758bd774-4v66h app[][o.s.a.SchedulerImpl] Waiting for initialization from 10.131.1.18
2024.01.17 23:54:42 WARN  sonarqube-dce-sonarqube-dce-app-56758bd774-4v66h app[][c.h.i.s.t.TcpServerConnectionErrorHandler] [10.131.2.95]:9003 [SonarQube] [5.3.2] Removing connection to endpoint [10.131.1.18]:9003 Cause => java.io.IOException {Connection refused to address /10.131.1.18:9003}, Error-Count: 5
2024.01.17 23:54:42 WARN  sonarqube-dce-sonarqube-dce-app-56758bd774-4v66h app[][c.h.i.c.i.MembershipManager] [10.131.2.95]:9003 [SonarQube] [5.3.2] Member [10.131.1.18]:9003 - f4203921-86dc-4cc6-8865-b1f60b46fe0d is suspected to be dead for reason: No connection

Hi,

Welcome to the community!

First, if you’re using DCE, then you have access to professional support. They’ll do a lot better helping you get DCE up and running.

That said, this is pretty clear:

 
HTH,
Ann