Sonar start and stop automatically but in sonar log file exit with elastic code 1

SonarQube Server / Community Build
, ,
1

My sonar.logs file output as follows
2023.07.06 06:37:05 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.07.06 06:37:07 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2023.07.06 06:37:07 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.07.06 06:37:07 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
2023.07.06 15:11:17 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2023.07.06 15:11:17 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:40479]
2023.07.06 15:11:17 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2023.07.06 15:11:17 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.07.06 15:11:19 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1

Specification of system as follows.

  • SonarQube deployed in aws ec2 instance with 4 gb ram and 2 core cpu.
  • Sonar version installed is -9.6.1.59531
  • Java version:- openjdk version “11.0.19” 2023-04-18 LTS
2

What do the other log files say?

:warning: Make sure you upgrade to SonarQube v9.9 LTS soon, not only to benefit from our Best LTS Ever™, but because soon we will systematically ask users to upgrade when they ask questions about earlier versions of SonarQube, which are now considered unsupported. :smiley: