Upgrading from 9.2 to 9.9

I am trying to upgrade from sonarqube-9.2.1.49989 to sonarqube-10.1.0.73491 but i get this error.
I tried to upgrade to sonarqube-9.9.1.69595 and have the exact same error.

Can someone help please ?

C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\bin\windows-x86-64>StartSonar.bat
Starting SonarQube...
2023.07.19 11:26:37 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\temp
2023.07.19 11:26:37 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:61531]
2023.07.19 11:26:37 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\elasticsearch]: C:\_Ateo_\TeamCity\jdk-17.0.1\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\temp -XX:ErrorFile=C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\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:\_Ateo_\Sonar\sonarqube-9.9.1.69595\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:\_Ateo_\Sonar\sonarqube-9.9.1.69595\elasticsearch -Des.path.conf=C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2023.07.19 11:26:37 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.07.19 11:26:49 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
2023.07.19 11:26:49 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [C:\_Ateo_\Sonar\sonarqube-9.9.1.69595]: C:\_Ateo_\TeamCity\jdk-17.0.1\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\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.1.69595.jar;C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\lib\jdbc\mssql\mssql-jdbc-11.2.2.jre17.jar org.sonar.server.app.WebServer C:\_Ateo_\Sonar\sonarqube-9.9.1.69595\temp\sq-process7638408868964938785properties
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:/_Ateo_/Sonar/sonarqube-9.9.1.69595/lib/sonar-application-9.9.1.69595.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.07.19 11:26:54 INFO  app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2023.07.19 11:26:54 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.07.19 11:26:54 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Hi,

Welcome to the community!

What do your server logs say?

 
Ann

sonar_10-1.zip (102.6 KB)
here are all my logs

Hi,

Going back to your OP… You talk about an error, but the log snippet you show only reflects a WARNING, which you can safely ignore.

The logs you provided are from 10.1. This thread started with trying to upgrade from 9.2.1. You said you got the same error when you tried to upgrade to 9.9.1.

The correct upgrade path from 9.2.1 is first 9.9.1 and then 10.1.

So when you go from 9.2.1 to 9.9.1, does the server start up as expected?

 
Ann

Yes. Server 9.9.1 is working fine.
I think we should ignore this thread. I have created another one here