Sonarqube no longer starting

Sonar previously installed and working. Now when I try to start it, I get:

2024.07.03 12:50:58 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2024.07.03 12:50:58 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [D:\Sonar2\sonarqube-10.2.0.77647]: C:\Program Files\Java\jdk-17\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=D:\Sonar2\sonarqube-10.2.0.77647\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 -Xmx1G -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-10.2.0.77647.jar;D:\Sonar2\sonarqube-10.2.0.77647\lib\jdbc\mssql\mssql-jdbc-12.2.0.jre11.jar org.sonar.server.app.WebServer D:\Sonar2\sonarqube-10.2.0.77647\temp\sq-process11619608379031111923properties
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.sonar.process.PluginSecurityManager (file:/D:/Sonar2/sonarqube-10.2.0.77647/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
2024.07.03 12:51:10 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2024.07.03 12:51:10 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.07.03 12:51:10 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

Hi @tomgray09,

Can you check your $SQ_HOME/logs folder and share what you see?

Please attach your sonar.log and web.log here for us to review.

1 Like

Yes, and apologies for the delay. I’ll attach the logs. It looks like SQ is unable to make the connection to the SQL Server instance.