I’ve installed and started SonarQube 2025.1 Community Build (sonarqube-25.1.0.102122.zip). Then I opened SQ URL in the browser to upgrade database but when I’m pressing “Start upgrade” button nothing is happening. I tried different browsers, tried to access with and without reverse-proxy, nothing helped so far. What can be the issue and how to fix it?
You can see the relevant piece from the access.log file below. I suspect there shouldn’t be an undefined in the POST - “/undefined/api/system/migrate_db”, or I’m wrong?
Hi Ann,
There is the last records from the log files.
sonar.log
2025.01.28 15:35:12 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2025.01.28 15:35:12 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [X:\XXXX\sonarqube-25.1.0.102122]: X:\XXXX\JDK\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=x:\xxxx\SonarHome\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 -server -Xmx768m -Xms256m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-25.1.0.102122.jar;X:\XXXX\sonarqube-25.1.0.102122\lib\jdbc\mssql\mssql-jdbc-11.2.2.jre17.jar org.sonar.server.app.WebServer x:\xxxx\SonarHome\temp\sq-process16258872114616849532properties
2025.01.28 15:35:16 WARN app[][startup] ################################################################################
2025.01.28 15:35:16 WARN app[][startup] The database must be manually upgraded. Please backup the database and browse /setup. For more information: https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/upgrade-the-server/roadmap
2025.01.28 15:35:16 WARN app[][startup] ################################################################################
web.log
2025.01.28 15:35:21 INFO web[][o.s.s.e.EsClientProvider] Connected to local Elasticsearch: [http://127.0.0.1:9001]
2025.01.28 15:35:22 INFO web[][o.s.s.p.Platform] Database needs to be migrated. Please refer to https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/upgrade-the-server/roadmap
2025.01.28 15:35:22 INFO web[][o.s.s.p.w.MasterServletFilter] Initializing servlet filter org.sonar.server.platform.web.WebServiceFilter@35e2b89f [pattern=UrlPattern{inclusions=[/api/system/migrate_db.*, ...], exclusions=[/api/components/update_key, ...]}]
2025.01.28 15:35:24 INFO web[][o.h.v.i.util.Version] HV000001: Hibernate Validator null
es.log
2025.01.28 15:35:11 INFO es[][o.e.l.ClusterStateLicenseService] license [f2eec4ee-4c3d-417e-b60d-371dfbeb5f12] mode [basic] - valid
2025.01.28 15:35:11 INFO es[][o.e.c.f.AbstractFileWatchingService] starting file watcher ...
2025.01.28 15:35:11 INFO es[][o.e.g.GatewayService] recovered [0] indices into cluster_state
2025.01.28 15:35:11 INFO es[][o.e.c.f.AbstractFileWatchingService] file settings service up and running [tid=39]
2025.01.28 15:35:12 INFO es[][o.e.r.s.FileSettingsService] setting file [x:\xxxx\SonarHome\temp\conf\es\operator\settings.json] not found, initializing [file_settings] as empty
2025.01.28 15:35:12 INFO es[][o.e.h.n.s.HealthNodeTaskExecutor] Node [{sonarqube}{aJ9BVlGcRz-xzENxKF3-Ig}] is selected as the current health node.
Nothing happens when I click the upgrade button. Nothing at all.
Of all server logs new records appear in access.log only, which I already shared in previous reply.
In browser console I see a single message -
Unexpected status code: undefined
Rp.console.error @ index.js:6726
Hi Ann,
Running curl -X POST https://server.domain.com/api/system/migrate_db is helped to upgrade database, but isn’t helped to get SonarQube in working condition.
2025.01.31 10:46:06 INFO web[][o.s.s.p.w.MasterServletFilter] Initializing servlet filter org.sonar.server.saml.ws.ValidationAction@7d6393cd [pattern=UrlPattern{inclusions=[/saml/validation], exclusions=[]}]
2025.01.31 10:46:06 INFO web[][o.s.s.p.w.MasterServletFilter] Initializing servlet filter org.sonar.server.user.ws.ChangePasswordAction@47bb9d73 [pattern=UrlPattern{inclusions=[/api/users/change_password], exclusions=[]}]
2025.01.31 10:46:06 INFO web[][o.s.s.p.w.MasterServletFilter] Initializing servlet filter org.sonar.server.plugins.PluginsRiskConsentFilter@5bce75f [pattern=UrlPattern{inclusions=[/*], exclusions=[*.css, ...]}]
2025.01.31 10:46:06 INFO web[][o.s.s.p.p.PlatformLevelStartup] Running Community Edition
2025.01.31 10:46:07 INFO web[][o.s.s.p.Platform] Web Server is operational
es.log
2025.01.31 10:45:53 INFO es[][o.e.l.ClusterStateLicenseService] license [f2eec4ee-4c3d-417e-b60d-371dfbeb5f12] mode [basic] - valid
2025.01.31 10:45:53 INFO es[][o.e.c.f.AbstractFileWatchingService] starting file watcher ...
2025.01.31 10:45:53 INFO es[][o.e.g.GatewayService] recovered [6] indices into cluster_state
2025.01.31 10:45:53 INFO es[][o.e.c.f.AbstractFileWatchingService] file settings service up and running [tid=39]
2025.01.31 10:45:53 INFO es[][o.e.r.s.FileSettingsService] setting file [c:\path\SonarHome\temp\conf\es\operator\settings.json] not found, initializing [file_settings] as empty
2025.01.31 10:45:53 INFO es[][o.e.h.n.s.HealthNodeTaskExecutor] Node [{sonarqube}{aJ9BVlGcRz-xzENxKF3-Ig}] is selected as the current health node.
2025.01.31 10:45:54 INFO es[][o.e.c.r.a.AllocationService] current.health="GREEN" message="Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[metadatas][0]]])." previous.health="RED" reason="shards started [[metadatas][0]]"
ce.log
2025.01.31 10:46:50 INFO ce[][o.s.c.t.CeWorkerImpl] Execute task | project=GFE | type=ISSUE_SYNC | branch=master | branchType=BRANCH | id=56b254f3-9069-4ed2-9b1e-b3dc2f706aaa
2025.01.31 10:46:50 INFO ce[56b254f3-9069-4ed2-9b1e-b3dc2f706aaa][o.s.c.t.s.ComputationStepExecutor] Ignore orphan component | status=SUCCESS | time=9ms
2025.01.31 10:46:50 INFO ce[56b254f3-9069-4ed2-9b1e-b3dc2f706aaa][o.s.c.t.p.t.IndexIssuesStep] indexing issues of branch AYLGZmR5cpQZi88PFSx5
2025.01.31 10:46:50 INFO ce[56b254f3-9069-4ed2-9b1e-b3dc2f706aaa][o.s.c.t.s.ComputationStepExecutor] index issues | status=SUCCESS | time=27ms
2025.01.31 10:46:50 INFO ce[56b254f3-9069-4ed2-9b1e-b3dc2f706aaa][o.s.c.t.CeWorkerImpl] Executed task | project=GFE | type=ISSUE_SYNC | branch=master | branchType=BRANCH | id=56b254f3-9069-4ed2-9b1e-b3dc2f706aaa | status=SUCCESS | time=67ms
sonar.log
2025.01.31 10:46:07 INFO app[][o.s.a.SchedulerImpl] Process[web] is up
2025.01.31 10:46:07 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[COMPUTE_ENGINE] from [C:\path\sonarqube-25.1.0.102122]: C:\path\JDK\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=c:\path\SonarHome\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=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 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-25.1.0.102122.jar;C:\path\sonarqube-25.1.0.102122\lib\jdbc\mssql\mssql-jdbc-12.8.1.jre11.jar org.sonar.ce.app.CeServer c:\path\SonarHome\temp\sq-process9436399417092576535properties
2025.01.31 10:46:11 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
2025.01.31 10:46:11 INFO app[][o.s.a.SchedulerImpl] SonarQube is operational
I have double-checked our customizations, and it turns out that the issue is caused by the custom footer in the web/index.html file. Thank you for your help.