Sonarqube upgrade from version 7.9 to 8.9 is getting stuck

SonarQube Server / Community Build
, , ,
1

Make sure to tell us:

  • What version are you upgrading from?
    i am upgrading from 7.9 to 8.9
  • System information (Operating system, Java version, Database provider/version)
    windows server 2016, amazon corretto 17, MSSQL 2017.5
  • What’s the issue you’re facing?
    I have don all the formalities of pre-upgrade but when i am trying to run from “startsonar.bat” the output is getting stuck at particular point. below is the log which is getting generated.

F:\sonarqube-8.9\sonarqube-8.9.10.61524\bin\windows-x86-64>StartSonar.bat
wrapper | → Wrapper Started as Console
wrapper | Launching a JVM…
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2024.02.17 15:36:10 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory F:\sonarqube-8.9\sonarqube-8.9.10.61524\temp
jvm 1 | 2024.02.17 15:36:10 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:50056]
jvm 1 | 2024.02.17 15:36:10 INFO app[o.s.a.ProcessLauncherImpl] Launch process[[key=‘es’, ipcIndex=1, logFilenamePrefix=es]] from [F:\sonarqube-8.9\sonarqube-8.9.10.61524\elasticsearch]: C:\Program Files\Amazon Corretto\jdk17.0.10_7\bin\java -XX:+UseG1GC -Djava.io.tmpdir=F:\sonarqube-8.9\sonarqube-8.9.10.61524\temp -XX:ErrorFile=…/logs/es_hs_err_pid%p.log -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djna.tmpdir=F:\sonarqube-8.9\sonarqube-8.9.10.61524\temp -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=COMPAT -Des.enforce.bootstrap.checks=true -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=F:\sonarqube-8.9\sonarqube-8.9.10.61524\elasticsearch -Des.path.conf=F:\sonarqube-8.9\sonarqube-8.9.10.61524\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
jvm 1 | 2024.02.17 15:36:10 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2024.02.17 15:36:22 INFO app[o.s.a.SchedulerImpl] Process[es] is up
jvm 1 | 2024.02.17 15:36:22 INFO app[o.s.a.ProcessLauncherImpl] Launch process[[key=‘web’, ipcIndex=2, logFilenamePrefix=web]] from [F:\sonarqube-8.9\sonarqube-8.9.10.61524]: C:\Program Files\Amazon Corretto\jdk17.0.10_7\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=F:\sonarqube-8.9\sonarqube-8.9.10.61524\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 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-8.9.10.61524.jar;F:\sonarqube-8.9\sonarqube-8.9.10.61524\lib\jdbc\mssql\mssql-jdbc-9.2.0.jre11.jar org.sonar.server.app.WebServer F:\sonarqube-8.9\sonarqube-8.9.10.61524\temp\sq-process8392888865602627559properties

2

What do the other log files say?

3

Hi, Thanks for the response.
The issue got resolved after adding the suggested .dll for jdbc but now I am upgrading from 8.9 to 9.9 and the sonarqube stops with below logs Not able to figure out why is this happening, when we start sonarqube without adding my sql server property it runs fine but as soon as I apply my database configuration it fails

Your help is much appreciated

C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\bin\windows-x86-64>StartSonar.bat

Starting SonarQube…

2024.02.21 10:36:47 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\temp

2024.02.21 10:36:47 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:62870]

2024.02.21 10:36:47 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\elasticsearch]: C:\Program Files\Amazon Corretto\jdk17.0.10_7\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\temp -XX:ErrorFile=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\logs\es_hs_err_pid%p.log -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djna.tmpdir=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\temp -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=COMPAT -Dcom.redhat.fips=false -Des.enforce.bootstrap.checks=true -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\elasticsearch -Des.path.conf=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch

2024.02.21 10:36:47 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running

2024.02.21 10:36:55 INFO app[o.s.a.SchedulerImpl] Process[es] is up

2024.02.21 10:36:55 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374]: C:\Program Files\Amazon Corretto\jdk17.0.10_7\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\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-9.9.4.87374.jar;C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\lib\jdbc\mssql\mssql-jdbc-11.2.2.jre17.jar org.sonar.server.app.WebServer C:\Users\tfsservice\Desktop\sonarqube-9.9.4.87374\sonarqube-9.9.4.87374\temp\sq-process15010231421820979968properties

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/tfsservice/Desktop/sonarqube-9.9.4.87374/sonarqube-9.9.4.87374/lib/sonar-application-9.9.4.87374.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.02.21 10:36:58 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped

2024.02.21 10:36:58 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped

2024.02.21 10:36:58 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

4

What does it say in the web.log log file?

It’s generally a good practice to check all the log files when you’re running into an issue.