Hello! Im having problems with starting my sonarqube server. When running the SonarStart.bat, it never shows the message “Sonarqube is up” and accessing the port where it is supposed to be, it stays forever loading with the message “SonarQube is starting”. My logs dont show any error that gets my attention and I already tried lots of solutions including the ones that are here in the community. Can anyone help? Im using sonarqube-10.6.0.92116 and my log files are attached. My prompt shows this:
Starting SonarQube...
2024.06.25 20:28:50 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\temp
2024.06.25 20:28:50 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:57764]
2024.06.25 20:28:50 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\elasticsearch]: C:\Program Files\Java\jdk-17\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\elasticsearch -Des.path.conf=C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\temp\conf\es -Des.distribution.type=tar -cp C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\elasticsearch\lib\*;C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\elasticsearch\lib\cli-launcher\* org.elasticsearch.launcher.CliToolLauncher
2024.06.25 20:28:50 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.06.25 20:29:09 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2024.06.25 20:29:09 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116]: C:\Program Files\Java\jdk-17\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\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 --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-10.6.0.92116.jar;C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\lib\jdbc\mssql\mssql-jdbc-12.6.1.jre11.jar org.sonar.server.app.WebServer C:\Users\pedro\sonarQube\sonarqube-10.6.0.92116\temp\sq-process5200363876005296731properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/C:/Users/pedro/sonarQube/sonarqube-10.6.0.92116/lib/sonar-application-10.6.0.92116.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
logs.zip (10.4 KB)
Welcome 
seems you did an update from a former Sonarqube version.
The update process stops at the point where you need to initiate the database update.
see sonar.log
2024.06.25 20:15:40 WARN app[][startup] ################################################################################
2024.06.25 20:15:40 WARN app[][startup] The database must be manually upgraded. Please backup the database and browse /setup. For more information: https://docs.sonarsource.com/sonarqube/latest/setup/upgrading
2024.06.25 20:15:40 WARN app[][startup] ################################################################################
This mean you need to browse https://<yoursonarhost>/setup and confirm the DB update.
Gilbert
1 Like
Hey! Thank you for your reply! I already did that update and actually, even when i use the embedded database it happens… my localhost:9000/setup says the database is up to date 
I believe the logs that must be taken into account are the last ones according to the timestamp
At a second glance i noticed only this in es.log
INFO es[][o.e.c.r.a.DiskThresholdMonitor] low disk watermark [85%]
but elasticsearch starts.
You can’t update the embedded database, try with deleting the contents of %SONARQUBE_HOME%/data, then restart
To get more insight you may set the loglevel to DEBUG before restart, see
%SONARQUBE_HOME%/conf/sonar.properties see property sonar.log.level and set
sonar.log.level=DEBUG
1 Like
Already did it all. The only thing that catches my attention is that in the sonar log this shows up:
java.net.ConnectException: Connection refused: no further information
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
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(Thread.java:842)
Can it be the case of the loop loading?
The web.log and sonar.log in debug level files are attached
logs.zip (26.0 KB)
Noticed this in the web.log
2024.06.26 18:52:15 DEBUG web[][c.m.s.jdbc.Driver] Microsoft JDBC Driver 12.6.3.0 for SQL Server
did you change the mssql jdbc driver !?
Normally with Sonarqube 10.6.0 the log has
2024.06.27 00:04:38 DEBUG web[][c.m.s.jdbc.Driver] Microsoft JDBC Driver 12.6.1.0 for SQL Server
as Sonarqube 10.6.0 ships with sonarqube-10.6.0.92116\lib\jdbc\mssql\mssql-jdbc-12.6.1.jre11.jar
Yeah, I did change it. But changed back to mssql-jdbc-12.6.1.jre11.jar and the error persists. I really dont know what else to do haha. Cant it be because of the failed connections with port 9001? I already created rules to allow connections on the firewall and nothing seems to work
Did you already try to change the port ?
Yup! Going to attach my sonar.properties
sonar.zip (7.7 KB)
Did you try with Sonarqube 10.6.0 out of the box, means unzip and start !?
The sonar.properties has some changed entries, i.e.
# User credentials.
# Permissions to create tables, indices and triggers must be granted to JDBC user.
# The schema must be created first.
sonar.jdbc.username=
sonar.jdbc.password=
the sonar.jdbc properties have no values
# Use the following connection string if you want to use SQL Auth while connecting to MS Sql Server.
# Set the sonar.jdbc.username and sonar.jdbc.password appropriately.
sonar.jdbc.url=jdbc:sqlserver://localhost;databaseName=sonarqube;encrypt=false;trustServerCertificate=true;hostNameInCertificate=*;
not sure if this jdbc connection string is correct.
i use mssql with integrated security
# Binding IP address. For servers with more than one IP address, this property specifies which
# address will be used for listening on the specified ports.
# By default, ports will be used on all IP addresses associated with the server.
sonar.web.host=127.0.0.1
normally it’s (i didn’t change it)
#sonar.web.host=0.0.0.0