Process exited with exit value [ElasticSearch]: 1 Process[ElasticSearch] is stopped SonarQube is sto

SonarQube
,
1

I was trying to run SonarQube community version on my computer, when after downloading JDK 19, I got the following log.

2023.03.01 14:56:54 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\ServerSonar\sonarqube-9.9.0.65466\temp
2023.03.01 14:56:54 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:62060]
2023.03.01 14:56:54 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\ServerSonar\sonarqube-9.9.0.65466\elasticsearch]: C:\Program Files\Java\jdk-19\bin\java -XX:+UseG1GC -Djava.io.tmpdir=C:\ServerSonar\sonarqube-9.9.0.65466\temp -XX:ErrorFile=C:\ServerSonar\sonarqube-9.9.0.65466\logs\es_hs_err_pid%p.log -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -Djna.tmpdir=C:\ServerSonar\sonarqube-9.9.0.65466\temp -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=COMPAT -Dcom.redhat.fips=false -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\ServerSonar\sonarqube-9.9.0.65466\elasticsearch -Des.path.conf=C:\ServerSonar\sonarqube-9.9.0.65466\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
2023.03.01 14:56:54 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.03.01 14:56:54 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2023.03.01 14:56:54 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.03.01 14:56:54 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Then I saw similar problems and they said it was a version problem, so I tried to change to version 17 and it didn’t even give me an error but it just opened and closed the console instantly. I also tried with version 18 and got the same result. What can I do?

2

Hi,

Welcome to the community!

I’m not surprised it didn’t run with Java 19. It should work with Java 17. If it’s not, you need to check your server logs.

 
Ann

3

2023.08.10 09:09:38 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\temp
2023.08.10 09:09:38 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:10208]
2023.08.10 09:09:38 INFO app[o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\elasticsearch]: C:\Program Files\Java\jdk-17\bin\java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\elasticsearch -Des.path.conf=C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\temp\conf\es -Des.distribution.type=tar -cp C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\elasticsearch\lib*;C:\sonarqube-enterprise-10.1.0.73491\sonarqube-10.1.0.73491\elasticsearch\lib\cli-launcher* org.elasticsearch.launcher.CliToolLauncher
2023.08.10 09:09:38 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.08.10 09:09:52 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2023.08.10 09:09:52 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.08.10 09:09:52 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped.

we are facing an error. SonarQube start while.