I am trying to install SonarQube Community Edition 10.5 in Windows 11 machine and have set SONAR_JAVA_PATH as well in environmental variables. On executing the StartSonar.bat file there’s no response.
In the Log files immediately after when “Process is up” is displayed we get the following response - Launch process[WEB_SERVER] from [C:\sonarqube-10.5.1.90531 (1)\sonarqube-10.5.1.90531]: C:\Program Files\Java\jdk-17\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\sonarqube-10.5.1.90531 (1)\sonarqube-10.5.1.90531\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens=java.management/sun.management=ALL-UNNAMED --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED -Dcom.redhat.fips=false -Xmx1024m -Xms1024m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/sonar-application-10.5.1.90531.jar;C:\sonarqube-10.5.1.90531 (1)\sonarqube-10.5.1.90531\lib\jdbc\h2\h2-2.2.224.jar org.sonar.server.app.WebServer C:\sonarqube-10.5.1.90531 (1)\sonarqube-10.5.1.90531\temp\sq-process3156830088908900529properties
After this we can see the following response -
2024.06.03 16:01:08 INFO app[o.s.a.SchedulerImpl] Process[Web Server] is stopped
2024.06.03 16:01:09 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2024.06.03 16:01:09 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
We are not able to find what is the exact cause that why is the application not running.
I was able to found a warning on es.log file stating - 2024.06.03 12:12:49 WARN es[][o.e.c.r.a.DiskThresholdMonitor] high disk watermark [90%] exceeded on [o6Wx0DJ6TTyGTodKjsbR5Q][sonarqube][C:\sonarqube-10.5.1.90531 (1)\sonarqube-10.5.1.90531\data\es8] free: 6.8gb[5.7%], shards will be relocated away from this node; currently relocating away shards totalling [0] bytes; the node is expected to continue to exceed the high disk watermark when these relocations are complete
And in sonar.log - 2024.06.03 16:28:35 WARN web[][o.s.c.a.AnnotationConfigApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@659e0bfd-org.sonar.server.es.IndexCreator': Initialization of bean failed; nested exception is org.sonar.server.es.ElasticsearchException: Fail to execute es requestES get request for key 'dbVendor' on index 'metadatas'
2024.06.03 16:28:35 ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@659e0bfd-org.sonar.server.es.IndexCreator': Initialization of bean failed; nested exception is org.sonar.server.es.ElasticsearchException: Fail to execute es requestES get request for key 'dbVendor' on index 'metadatas'
Do the above sonar.log and es.log exceptions and failures refer to memory issue ?