SonarQube Server failed to start on the windows machine

  • I am using latest version of SonarQube Server Version 10.8 and java version is given below-
    openjdk 17.0.13 2024-10-15
    OpenJDK Runtime Environment Temurin-17.0.13+11 (build 17.0.13+11)
    OpenJDK 64-Bit Server VM Temurin-17.0.13+11 (build 17.0.13+11, mixed mode, sharing)

  • SonarQube is deployed as a zip file on the windows machine having windows 11 home edition.

  • While trying to start the SonarQube server on the windows machine using StartSonar.bat in command line admin mode, got the error and server failed to start

  • I have tried changing different versions of java (v11, v23) but no luck.

  • Error log is given below-

C:\Sonarqube\bin\windows-x86-64>StartSonar.bat
Starting SonarQube...
2025.01.21 12:29:09 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Sonarqube\temp
2025.01.21 12:29:09 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:{}]
2025.01.21 12:29:10 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\Sonarqube\elasticsearch]: C:\Program Files\Eclipse Adoptium\jdk-17.0.13.11-hotspot\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=C:\Sonarqube\elasticsearch -Des.path.conf=C:\Sonarqube\temp\conf\es -Des.distribution.type=tar -cp C:\Sonarqube\elasticsearch\lib\*;C:\Sonarqube\elasticsearch\lib\cli-launcher\* org.elasticsearch.launcher.CliToolLauncher
2025.01.21 12:29:10 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2025.01.21 12:29:55 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2025.01.21 12:29:55 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\Sonarqube]: C:\Program Files\Eclipse Adoptium\jdk-17.0.13.11-hotspot\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\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 --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 -Djava.security.manager=allow -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-25.1.0.102122.jar;C:\Sonarqube\lib\jdbc\mssql\mssql-jdbc-12.8.1.jre11.jar org.sonar.server.app.WebServer C:\Sonarqube\temp\sq-process12532271667240456785properties
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:/Sonarqube/lib/sonar-application-25.1.0.102122.jar)
WARNING: Please consider reporting this to the maintainers of org.sonar.process.PluginSecurityManager
WARNING: System::setSecurityManager will be removed in a future release
Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2025.01.21 12:30:01 INFO  app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2025.01.21 12:30:01 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025.01.21 12:30:01 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Other log files are-
es.log (10.8 KB)
sonar.log (2.2 KB)
web.log (10.9 KB)
SonarServiceWrapper.wrapper.log (64 Bytes)

Any type of help would be appreciated.

Thanks,
Narendra

Hi Narendra,

Welcome to the community!

Thanks for posting the logs. Did you read them?

 
Ann

Post fixing the DB connection issue, this issue has been resolved for me.

1 Like

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