Why sonar start failure?

sonarqube

(springage) #1

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension) 7.7
  • error observed (wrap logs/code around triple quote ``` for proper formatting)
    tail -f sonar.log
    Launching a JVM…
    Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
    Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.

2019.03.22 21:42:58 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube-7.7/temp
2019.03.22 21:42:58 INFO app[o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
2019.03.22 21:42:58 INFO app[o.s.a.p.ProcessLauncherImpl] Launch process[[key=‘es’, ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube-7.7/elasticsearch]: /opt/sonarqube-7.7/elasticsearch/bin/elasticsearch
2019.03.22 21:42:58 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2019.03.22 21:42:59 INFO app[o.e.p.PluginsService] no modules loaded
2019.03.22 21:42:59 INFO app[o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.03.22 21:43:11 INFO app[o.s.a.SchedulerImpl] Process[es] is up
2019.03.22 21:43:11 INFO app[o.s.a.p.ProcessLauncherImpl] Launch process[[key=‘web’, ipcIndex=2, logFilenamePrefix=web]] from [/opt/sonarqube-7.7]: /usr/local/java/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube-7.7/temp -Xmx2048m -Xms2048m -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*:/opt/sonarqube-7.7/lib/jdbc/mysql/mysql-connector-java-5.1.46.jar org.sonar.server.app.WebServer /opt/sonarqube-7.7/temp/sq-process4973925332334792043properties
2019.03.22 21:43:15 INFO app[o.s.a.SchedulerImpl] Process [web] is stopped
2019.03.22 21:43:15 INFO app[o.s.a.SchedulerImpl] Process [es] is stopped
2019.03.22 21:43:15 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
2019.03.22 21:43:15 WARN app[o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
<-- Wrapper Stopped

  • steps to reproduce
    install sonar would happen no matter config elastic or not.
  • potential workaround
    try to config the elastic cluster, not work, remove them, not work,neither
    P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

(Simon Brandhof) #2

Could you please check the error displayed in logs/web.log?