SonarQube 10.2 failed to start after upgraded from 10.1

  • SonarQube 10.2
  • How is SonarQube deployed: zip
  • Upgrade SonarQube from 10.1 to 10.2
  • What we have tried:
    ** Downloaded the zip of 10.2, unzipped, and start the service. Not running
    ** Reverted back to 10.1, it works fine.

Here are the console output:

E:\sonarqube\bin\windows-x86-64>StartSonar.bat
Starting SonarQube…
2023.09.10 18:30:24 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory E:\sonardata\temp
2023.09.10 18:30:24 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:50232]
2023.09.10 18:30:24 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [E:\sonarqube\elasticsearch]: C:\Program Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=E:\sonarqube\elasticsearch -Des.path.conf=E:\sonardata\temp\conf\es -Des.distribution.type=tar -cp E:\sonarqube\elasticsearch\lib*;E:\sonarqube\elasticsearch\lib\cli-launcher* org.elasticsearch.launcher.CliToolLauncher
2023.09.10 18:30:24 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.09.10 18:30:37 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2023.09.10 18:30:37 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [E:\sonarqube]: C:\Program Files\Eclipse Adoptium\jdk-17.0.5.8-hotspot\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=E:\sonardata\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 -Dcom.redhat.fips=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-10.2.0.77647.jar;E:\sonarqube\lib\jdbc\mssql\mssql-jdbc-12.2.0.jre11.jar org.sonar.server.app.WebServer E:\sonardata\temp\sq-process18256034285477053908properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/E:/sonarqube/lib/sonar-application-10.2.0.77647.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
2023.09.10 18:30:40 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.09.10 18:30:40 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.09.10 18:30:40 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

Hi,

Unfortunately the console log isn’t useful, you’ll need to check the log files.

Ah right, thanks for pointing to the right direction.

We just found out there was a typo in the SQL connection string.

All working fine now. Thanks a lot!