Hello SonarQube Community,
I recently upgraded our SonarQube instance from version 9.9 LTA to 10.8.1 EE, hosted on GKE. The database is an external MS SQL server, and we’re using Helm for deployment. The upgrade process, including database migration(https://sonar.xxxxx.com/setup), took approximately 2-2.5 hours, but I encountered several issues after the upgrade.
During upgrade:
- Pod Restarts and Errors:
- During the upgrade, the pod restarted several times. I thought this would be normal during the upgrade, but the number of restarts seemed unusual compared to the 9.9 LTA upgrade.
- The pod is up after 3 restarts with same error as below mentioned.
- Elasticsearch also had some issues during startup, and the pod’s behavior is repeating.
After Upgrade :
Developers reached out mentioning that in SonarQube, access is granted at the group level, but users can no longer execute analysis unless permissions are explicitly given at the individual user level, even though they are part of the group. Is this behavior expected in 10.8.1, or is this a configuration issue?
- I deleted the Elasticsearch es8 folder, thinking that indexing was the issue, but the pod still takes around 50 minutes to be up after 7 restarts with the same error.
Pod logs:
</>
2025.02.12 02:01:53 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2025.02.12 02:02:10 INFO app[x][o.s.a.SchedulerImpl] Process[es] is up
2025.02.12 02:02:10 INFO app[x][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [/opt/sonarqube]: /opt/java/openjdk/bin/java -
2025.02.12 02:02:44 INFO app[][o.s.a.SchedulerImpl] Process[web] is up
2025.02.12 02:02:44 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[COMPUTE_ENGINE] from [/opt/sonarqube]: /opt/java/openjdk/bin/java -
application-10.8.1.101195.jar:/opt/sonarqube/lib/jdbc/mssql/mssql-jdbc-12.8.1.jre11.jar org.sonar.ce.app.CeServer /opt/sonarqube/temp properties
2025.02.12 02:02:54 INFO app[][o.s.a.SchedulerImpl] Process[ce] is up
2025.02.12 02:02:54 INFO app[][o.s.a.SchedulerImpl] SonarQube is operational
2025.02.12 02:04:45 INFO app[][o.s.a.SchedulerImpl] Stopping SonarQube
2025.02.12 02:04:45 INFO app[][o.s.a.SchedulerImpl] Sonarqube has been requested to stop
2025.02.12 02:04:45 INFO app[][o.s.a.SchedulerImpl] Stopping [Compute Engine] process...
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] Process[Compute Engine] is stopped
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] Stopping [Web Server] process...
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] Process[Web Server] is stopped
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] Stopping [ElasticSearch] process...
2025.02.12 02:04:46 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 143
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025.02.12 02:04:46 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
2025.02.12 02:08:36 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2025.02.12 02:08:36 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 1xxxxx, TCP: xxxxx]
2025.02.12 02:08:36 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/java/openjdk/bin/java -
org.elasticsearch.launcher.CliToolLauncher
2025.02.12 02:08:36 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2025.02.12 02:08:51 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
2025.02.12 02:08:51 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[WEB_SERVER] from [/opt/sonarqube]: /opt/java/openjdk/bin/java -
+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|xxxx-cp ./lib/sonar-application-10.8.1.101195.jar:/opt/sonarqube/lib/jdbc/mssql/mssql-jdbc-12.8.1.jre11.jar org.sonar.server.app.WebServer
2025.02.12 02:12:32 INFO app[][o.s.a.SchedulerImpl] Stopping SonarQube
2025.02.12 02:12:32 INFO app[][o.s.a.SchedulerImpl] Sonarqube has been requested to stop
2025.02.12 02:12:32 INFO app[][o.s.a.SchedulerImpl] Stopping [Compute Engine] process...
2025.02.12 02:12:32 INFO app[][o.s.a.SchedulerImpl] Stopping [Web Server] process
</>
system and DB details:
{
"Health": "GREEN",
"Health Causes": [],
"System": {
"Server ID": "",
"Version": "10.8.1.101195",
"Edition": "Enterprise",
"Lines of Code": xxxxx,
"Container": true,
"High Availability": false,
"Official Distribution": true,
"Force authentication": true,
"Home Dir": "/opt/sonarqube",
"Data Dir": "/opt/sonarqube/data",
"Temp Dir": "/opt/sonarqube/temp",
"Processors": 4
},
"Database": {
"Database": "Microsoft SQL Server",
"Database Version": "13.00.7029",
"Username": "sonarqube",
"URL": "jdbc:sqlserver://database:1433;",
"Driver": "Microsoft JDBC Driver 12.8 for SQL Server",
"Driver Version": "12.8.1.0",
"Default transaction isolation":
},
- The pod is taking longer than expected to become operational after es8 deletion to restart (higher than previous).
Has anyone encountered similar issues after upgrading from 9.9 LTA to 10.8.1? Any suggestions on how to resolve these problems would be greatly appreciate