which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
how is SonarQube deployed: zip, Docker, Helm
what are you trying to achieve
what have you tried so far to achieve this
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
Version: 10.4.1.88267
SonarQube unzipped and executed as per the online documentation
According to the docs running sonar.sh console should allow login via localhost:9000. However nothing binding to this port so there is no webserver running. ES is running on 9001 and can be reached without issue.
I have tried running sonar.sh console and sonar.sh start.I have also changed the binding IP and Port in the config but this does not make any difference.
We are trying to evaluate this against Semgrep and others, prior to investigating Enterprise licensing, and so far Sonarqube is the only one that has any issues.
2024.04.15 12:21:51 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-10.4.1.88267/temp
2024.04.15 12:21:51 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 172.29.166.101:9001, TCP: 172.29.166.101:32877]
2024.04.15 12:21:51 INFO app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube-10.4.1.88267/elasticsearch]: /usr/lib/jvm/java-21-openjdk-amd64/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube-10.4.1.88267/elasticsearch -Des.path.conf=/opt/sonarqube-10.4.1.88267/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube-10.4.1.88267/elasticsearch/lib/*:/opt/sonarqube-10.4.1.88267/elasticsearch/lib/cli-launcher/* org.elasticsearch.launcher.CliToolLauncher
2024.04.15 12:21:51 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running