Upgrade from sonarqube-8.3 to sonarqube-10.3.0.82913 is failing to start sonarqube server

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension):

JDK 17
Sonarqube-10.3.0.82913

  • how is SonarQube deployed: zip

  • what are you trying to achieve: Upgrade from sonarqube-8.3 to sonarqube-10.3.0.82913

  • what have you tried so far to achieve this:

  • Stopped all existing java services and sonar server before starting new sonar server

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

web.log:

2024.01.30 00:19:14 ERROR web[o.s.s.p.w.PlatformServletContextListener] Web server startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘jdk.internal.loader.ClassLoaders$AppClassLoader@659e0bfd-org.sonar.server.platform.DatabaseServerCompatibility’: Initialization of bean failed; nested exception is The version of SonarQube is too old. Please upgrade to the Long Term Support version first.

sonar.log
C:\sonarqube-10.3.0.82913\bin\windows-x86-64>StartSonar.bat status
Starting SonarQube…

2024.01.24 09:48:30 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sonarqube-10.3.0.82913\temp

2024.01.24 09:48:30 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:51664]

2024.01.24 09:48:30 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\sonarqube-10.3.0.82913\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:\sonarqube-10.3.0.82913\elasticsearch -Des.path.conf=C:\sonarqube-10.3.0.82913\temp\conf\es -Des.distribution.type=tar -cp C:\sonarqube-10.3.0.82913\elasticsearch\lib*;C:\s
onarqube-10.3.0.82913\elasticsearch\lib\cli-launcher* org.elasticsearch.launcher.CliToolLauncher

2024.01.24 09:48:30 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running

2024.01.24 09:48:42 INFO app[o.s.a.SchedulerImpl] Process[es] is up

2024.01.24 09:48:42 INFO app[o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\sonarqube-10.3.0.82913]: C:\Program Files\Java\jdk-17\bin\java -D
java.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\sonarqube-10.3.0.82913\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.3.0.82913.jar;C:\sonarqube-10.3.0.82913\lib\jdbc\postgresql\postgresql-42.6.0.jar org.sonar.server.app.WebServer C:\sonarqube-10.3.0.82913\temp\sq-process9323479069864617515properties
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-10.3.0.82913/lib/sonar-application-10.3.0.829
13.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.01.24 09:48:46 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped

2024.01.24 09:48:46 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped

2024.01.24 09:48:46 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

C:\sonarqube-10.3.0.82913\bin\windows-x86-64>

Hi,

Your update path is 8.3 > 8.9.10 former LTS > 9.9.3 LTS > 10.3
You must have all intermediate LTS versions in your update path.

see

see

for the former 8.9.10 LTS

Gilbert

1 Like

Thanks @Rebse Issue is fixed.