SonarQube is not running while updating 8.5 to 9.9 version

SonarQube Server / Community Build
, ,
1

Hi Team,
we tried to upgrade SonarQube version 8.5 to SonarQube 9.9 LTA version.
steps done
1.updated the sonar properties file
2.updated elasticsearch.yml file as like below

  • node.name: ${hostname}
  • network.host: 0.0.0.0

3.updated java 11 to 17 version and changed the environmental variable path to /usr/lib/jvm/java-17-openjdk-amd64/bin/java.
4.stoped the old sonarqube
5 started new sonarqube
getting the error as Removed stale pid file: ./SonarQube.pid
SonarQube is not running.
i have attached the sonar and es logs for your reference.
sonar and Es.log (7.7 KB)

2

Hey there.

Don’t do this.

SonarQube is not running while updating 8.5 to 9.9 version

Have you made sure to stop at the v8.9 version as documented in the upgrade guide?

3

Hi Colin
we are using SonarQube version 8.5 currently. For upgrading we first need to upgrade to 8.9 then 9.9.4 version or we can directly upgrade from 8.5 to 9.9.4 version. i tried to upgraded from 8.5 to 9.9.5 i am facing
error.txt (2.0 KB)
error .i have attached the error for your reference.

4

Yes, as documented.

5

we have upgraded to 9.0.1 version it is working fine, when we are trying to upgrade from 9.1 (java 11) to 9.9(java 17 and updated environmental path)we are facing the same issue .
log
2024.05.27 09:25:50 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.05.27 09:25:52 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2024.05.27 09:25:52 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.27 09:25:52 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
2024.05.27 09:27:18 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-9.9.5.90363/temp
2024.05.27 09:27:18 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:42453]
2024.05.27 09:27:18 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube-9.9.5.90363/elasticsearch]: /opt/sonarqube-9.9.5.90363/elasticsearch/bin/elasticsearch
2024.05.27 09:27:18 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.05.27 09:27:19 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2024.05.27 09:27:19 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.27 09:27:19 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
2024.05.27 09:33:34 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-9.9.5.90363/temp
2024.05.27 09:33:34 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:36561]
2024.05.27 09:33:34 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube-9.9.5.90363/elasticsearch]: /opt/sonarqube-9.9.5.90363/elasticsearch/bin/elasticsearch
2024.05.27 09:33:34 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2024.05.27 09:33:36 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2024.05.27 09:33:36 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.05.27 09:33:36 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped

6

The upgrade path is normally 8.5 → 8.9 → 9.9.

Why did you stop at 9.0.1 (or 9.1)?

7

In any case, make sure you check all the log files.

And here’s a good hint, make sure you aren’t running SonarQube as root.