Connectivity error after putting Database details

i have installed sonarqube 10.2 developer version and am using external RDS database instance . when i am trying to put database details /opt/sonarqube/conf/ my sonarqube stopped working . i am getting site not reached error in the browser

What do the logs say?

[root@ip-10-32-73-179 logs]# tail sonar.log
2024.04.04 13:49:37 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.04.04 13:49:37 INFO app[] Elasticsearch listening on [HTTP:, TCP:]
2024.04.04 13:49:38 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/jdk-17/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elasticsearch -Des.path.conf=/opt/sonarqube/temp/conf/es -Des.distribution.type=tar-cp /opt/sonarqube/elasticsearch/lib/:/opt/sonarqube/elasticsearch/lib/cli-launcher/ org.elasticsearch.launcher.CliToolLauncher
2024.04.04 13:49:38 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.04.04 13:49:56 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2024.04.04 13:49:56 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [/opt/sonarqube]: /opt/jdk-17/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/ --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/ -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application- /opt/sonarqube/temp/sq-process17414073937366529538properties
2024.04.04 13:50:02 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2024.04.04 13:50:02 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 143
2024.04.04 13:50:02 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.04.04 13:50:02 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

How about the other log files, like web.log?

[root@ip-10-32-73-179 logs]# tail es.log
2024.04.04 13:49:55 INFO es[o.e.l.LicenseService] license [84218088-2b66-44bc-b03e-874674696b1e] mode [basic] - valid
2024.04.04 13:49:55 INFO es[o.e.g.GatewayService] recovered [6] indices into cluster_state
2024.04.04 13:49:55 INFO es[o.e.h.n.s.HealthNodeTaskExecutor] Node [{sonarqube}{rYe-21n7QwKs8O_3MFdq5A}] is selected as the current health node.
2024.04.04 13:49:56 INFO es[o.e.c.r.a.AllocationService]“GREEN” message=“Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[metadatas][0]]]).”“RED” reason=“shards started [[metadatas][0]]”
2024.04.04 13:50:02 INFO es[o.e.n.Node] stopping …
2024.04.04 13:50:02 INFO es[o.e.r.s.FileSettingsService] shutting down watcher thread
2024.04.04 13:50:02 INFO es[o.e.r.s.FileSettingsService] watcher service stopped
2024.04.04 13:50:02 INFO es[o.e.n.Node] stopped
2024.04.04 13:50:02 INFO es[o.e.n.Node] closing …
2024.04.04 13:50:02 INFO es[o.e.n.Node] closed

2024.04.04 13:50:02 INFO es[o.e.n.Node] closed
[root@ip-10-32-73-179 logs]# tail web.log
at org.sonar.process.ProcessEntryPoint.launch(
at org.sonar.process.ProcessEntryPoint.launch(
Caused by: org.sonar.api.utils.MessageException: The version of SonarQube is too old. Please upgrade to the Long Term Support version first.
2024.04.04 13:50:02 INFO web[c.z.h.HikariDataSource] HikariPool-1 - Shutdown initiated…
2024.04.04 13:50:02 INFO web[c.z.h.HikariDataSource] HikariPool-1 - Shutdown completed.
2024.04.04 13:50:02 INFO web[o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000
2024.04.04 13:50:02 INFO web[o.s.p.ProcessEntryPoint] Hard stopping process
[root@ip-10-32-73-179 logs]#

It seems like you’re connecting to a database that previously had a SonarQube instance started against it. Is that the case?

i had privously 9.9 version of sonarqube then i removed i install new one 10.2. That casing issue?

Are you intending to upgrade, or start new?

i started with new only

Can you suggest me what should i do

Hello can you help me as soon as possible

Hey there.

If your goal is to start a fresh SonarQube instance, I would suggest:

  • Dropping the existing SonarQube database
  • Target SonarQube v10.4, which is the latest active version of SonarQube. v10.2 is EOL.

Done with all the steps that have you mentioned

after uncomment database details site goes down