Could not find java in ES_JAVA_HOME at /usr/bin/java

I am getting the same issue (although I have successfully launched the exact same container on a different host.) My logs include this detail:

[root@sonarqube-01 mnt]# docker logs -f sonarqube
Dropping Privileges
2022.01.17 03:43:08 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2022.01.17 03:43:08 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:41509]
2022.01.17 03:43:08 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
could not find java in ES_JAVA_HOME at /usr/lib/jvm/java-11-openjdk/bin/java
2022.01.17 03:43:08 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2022.01.17 03:43:08 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 1
2022.01.17 03:43:08 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
2022.01.17 03:43:08 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
Dropping Privileges

Here is some additional detail within failing container:

bash-5.1# bash -x elasticsearch/bin/elasticsearch
++ dirname elasticsearch/bin/elasticsearch
+ source elasticsearch/bin/elasticsearch-env
++ set -e -o pipefail
++ CDPATH=
++ SCRIPT=elasticsearch/bin/elasticsearch
++ '[' -h elasticsearch/bin/elasticsearch ']'
+++ dirname elasticsearch/bin/elasticsearch
++ ES_HOME=elasticsearch/bin
+++ cd elasticsearch/bin
+++ pwd
++ ES_HOME=/opt/sonarqube/elasticsearch/bin
+++ basename /opt/sonarqube/elasticsearch/bin
++ '[' bin '!=' bin ']'
+++ dirname /opt/sonarqube/elasticsearch/bin
++ ES_HOME=/opt/sonarqube/elasticsearch
++ ES_CLASSPATH='/opt/sonarqube/elasticsearch/lib/*'
++ '[' '!' -z /usr/lib/jvm/default-jvm ']'
++ JAVA=/usr/lib/jvm/default-jvm/bin/java
++ JAVA_TYPE=ES_JAVA_HOME
++ '[' '!' -x /usr/lib/jvm/default-jvm/bin/java ']'
++ echo 'could not find java in ES_JAVA_HOME at /usr/lib/jvm/default-jvm/bin/java'
could not find java in ES_JAVA_HOME at /usr/lib/jvm/default-jvm/bin/java
++ exit 1
bash-5.1# ls -la /usr/lib/jvm/default-jvm/bin/
total 216
drwxr-xr-x    2 root     root          4096 Dec 20 19:30 .
drwxr-xr-x    6 root     root          4096 Dec 20 19:30 ..
-rwxr-xr-x    1 root     root         14056 Dec  8 12:11 java
-rwxr-xr-x    1 root     root         14112 Dec  8 12:11 jjs
-rwxr-xr-x    1 root     root         14080 Dec  8 12:11 keytool
-rwxr-xr-x    1 root     root         14080 Dec  8 12:11 pack200
-rwxr-xr-x    1 root     root         14080 Dec  8 12:11 rmid
-rwxr-xr-x    1 root     root         14080 Dec  8 12:11 rmiregistry
-rwxr-xr-x    1 root     root        111168 Dec  8 12:11 unpack200
bash-5.1# java -version
openjdk version "11.0.12" 2021-07-20
OpenJDK Runtime Environment (build 11.0.12+7-alpine-r0)
OpenJDK 64-Bit Server VM (build 11.0.12+7-alpine-r0, mixed mode)
bash-5.1# which java
/usr/bin/java
bash-5.1# export ES_JAVA_HOME=/usr
bash-5.1# bash -x elasticsearch/bin/elasticsearch
++ dirname elasticsearch/bin/elasticsearch
+ source elasticsearch/bin/elasticsearch-env
++ set -e -o pipefail
++ CDPATH=
++ SCRIPT=elasticsearch/bin/elasticsearch
++ '[' -h elasticsearch/bin/elasticsearch ']'
+++ dirname elasticsearch/bin/elasticsearch
++ ES_HOME=elasticsearch/bin
+++ cd elasticsearch/bin
+++ pwd
++ ES_HOME=/opt/sonarqube/elasticsearch/bin
+++ basename /opt/sonarqube/elasticsearch/bin
++ '[' bin '!=' bin ']'
+++ dirname /opt/sonarqube/elasticsearch/bin
++ ES_HOME=/opt/sonarqube/elasticsearch
++ ES_CLASSPATH='/opt/sonarqube/elasticsearch/lib/*'
++ '[' '!' -z /usr ']'
++ JAVA=/usr/bin/java
++ JAVA_TYPE=ES_JAVA_HOME
++ '[' '!' -x /usr/bin/java ']'
++ echo 'could not find java in ES_JAVA_HOME at /usr/bin/java'
could not find java in ES_JAVA_HOME at /usr/bin/java

Hi @Jaff :wave:

i moved your reply to a dedicated thread as i am not sure if you are really facing the same problem as the other user.
For the behavior you described, you are hit by SONAR-15167. Please see that workarounds for this issue in this thread and let me know if you are still facing issues afterwards.

Just a guess but your other host has probably a more recent container runtime?

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.