- SonarQube Developer v9.4 ( I wish to downgrade to SonarQube -9.3 Community edition)
- Ubuntu 18
I have completed my 14 day trial of SonarQube's Developer edition, and I would like to downgrade to the community edition.
- I have stopped the Developer instance SonarQube
- I have started the Community instance of SonarQube
SonarQube’s Community edition is not running, and this is what my web.log file looks like.
2022.04.20 21:31:18 INFO web[][o.s.p.ProcessEntryPoint] Starting web
2022.04.20 21:31:18 INFO web[][o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read
2022.04.20 21:31:19 INFO web[][o.s.s.e.EsClientProvider] Connected to local Elasticsearch: [http://localhost:9001]
2022.04.20 21:31:19 INFO web[][o.s.s.p.LogServerVersion] SonarQube Server / 9.3.0.51899 / 1a276267d04cd4df862d57201082413946b6b3fa
2022.04.20 21:31:19 INFO web[][o.sonar.db.Database] Create JDBC data source for jdbc:postgresql://localhost/sonarqube
2022.04.20 21:31:20 INFO web[][o.s.s.p.ServerFileSystemImpl] SonarQube home: /opt/sonarqube/sonarqube-9.3.0.51899
2022.04.20 21:31:20 INFO web[][o.s.s.u.SystemPasscodeImpl] System authentication by passcode is disabled
2022.04.20 21:31:20 ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Database was upgraded to a more recent version of SonarQube. A backup must probably be restored or the DB settings are incorrect.
2022.04.20 21:31:20 INFO web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000
2022.04.20 21:31:20 INFO web[][o.s.p.ProcessEntryPoint] Hard stopping process
this is what my sonar.log file looks like
--> Wrapper Started as Daemon
Launching a JVM...
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
2022.04.20 21:31:06 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/sonarqube-9.3.0.51899/temp
2022.04.20 21:31:06 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:45727]
2022.04.20 21:31:06 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/sonarqube-9.3.0.51899/elasticsearch]: /opt/sonarqube/sonarqube-9.3.0.51899/elasticsearch/bin/elasticsearch
2022.04.20 21:31:06 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2022.04.20 21:31:17 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2022.04.20 21:31:17 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube/sonarqube-9.3.0.51899]: /opt/java/jdk-11/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/sonarqube-9.3.0.51899/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 -server -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-9.3.0.51899.jar:/opt/sonarqube/sonarqube-9.3.0.51899/lib/jdbc/postgresql/postgresql-42.3.1.jar org.sonar.server.app.WebServer /opt/sonarqube/sonarqube-9.3.0.51899/temp/sq-process9341720501987429993properties
2022.04.20 21:31:20 INFO app[][o.s.a.SchedulerImpl] Process[web] is stopped
2022.04.20 21:31:21 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped
2022.04.20 21:31:21 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143
2022.04.20 21:31:21 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
<-- Wrapper Stopped
Found this online here
If you do not have a backup, then there is no easy workaround. It might theoretically be possible to manually downgrade the database, but that is a super-risky and hard thing to do.
I do not have a backup of my database,
How can I get my community version up and running again?