Sonar does not open on localhost:9000

SonarQube Server / Community Build
1

Hey guys

I installed sonarqube 8.6 following the documentation and I’m having the following error:

After executing the command:

sudo systemctl start sonar.service

Only Elasticsearch is initialized at localhost:9001. Below is the opt/sonarqube/logs log

--> Wrapper Started as Daemon
Launching the JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.

2024.04.10 12:31:38 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2024.04.10 12:31:38 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:42433]
2024.04.10 12:31:38 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/ elasticsearch/bin/elasticsearch
2024.04.10 12:31:38 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
2024.04.10 12:31:41 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2024.04.10 12:31:41 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube]: /usr/lib/jvm/ java-11-openjdk-amd64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/temp -XX:-OmitStackTraceInFastThrow --add-opens =java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add- opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -Xmx2048m -Xms2048m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*: /opt/sonarqube/lib/jdbc/postgresql/postgresql-42.2.17.jar org.sonar.server.app.WebServer /opt/sonarqube/temp/sq-process11286657274784187144properties

When I try to access localhost:9000 to view the Sonar webserver, I only get a generic browser error.
I believe the sonar itself is not running
Checking the ports in use with the command

sudo netstat -tulpn

I only see the service on port 9001 of the ELK, but no use of port 9000.

Below is my configuration file

#--------------------------------------------------------------------------------------------------
# WEB SERVER

sonar.web.host=127.0.0.1
sonar.web.port=9000
sonar.web.http.maxThreads=50
sonar.web.http.minThreads=5
sonar.web.http.acceptCount=25
sonar.ajp.port=-1

#--------------------------------------------------------------------------------------------------
# Google SSO
#sonar.core.serverBaseURL=https://sonar.financial.esales.dev
#--------------------------------------------------------------------------------------------------
# COMPUTE ENGINE

sonar.ce.workerCount=1

#--------------------------------------------------------------------------------------------------
# ELASTICSEARCH

sonar.search.javaOpts=-Xmx2G -Xms2G -Djava.net.preferIPv4Stack=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiati>
sonar.search.javaAdditionalOpts=
sonar.search.port=9001
sonar.search.host=127.0.0.1
2

Hi,

Your version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

xxx → 8.9.10 → 9.9.4 → 10.4 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us.

Thanks,
Schyler

2 Likes
3

Thanks for the tip Schyler :smile:

However, I am having to maintain a legacy version of Sonar (an update is already in the plans).

Would you have any tips on how to better debug this problem to keep this EOL version working while it is not updated?

The answer is probably no, I will prioritize the migration…

4

Is there any additional information you can provide from the logs? Is the service startup indicating that all processes started up successfully (es, web, and ce)? Since the log output you provided ends on the web process launch, is there anything in the web.log that points at the issue?

5

I found the problem in the web logs, the server is unable to initiate a connection between the JDBC driver and the Postgres database server.

I updated the database server to version 16 of Postgres, I assume that version 8.6 does not have this compatibility, right?

Reading the documentation, I found the information that the version above mine, 8.9 LTS, supports Postgres 9.6 to 13.

That’s probably my problem, incompatibility between the web service and Postgres

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.