SonarQube web process not starting

elasticsearch

(Seumas Soltysik) #1

I have installed SonarQube 6.7.3 on RH 6x. However after installing when I start the server using “sonar.sh console”, the server process seems to hang on the elasticsearch startup. The output from sonar.log is as follows:

jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/staples/sonar/sonarqube-6.7.3/temp
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/staples/sonar/sonarqube-6.7.3/elasticsearch]: /opt/staples/sonar/sonarqube-6.7.3/elasticsearch/bin/elasticsearch -Epath.conf=/opt/staples/sonar/sonarqube-6.7.3/temp/conf/es
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.e.p.PluginsService] no modules loaded
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]

There is no further output from the console to indicate that the elastic search process has started and there are no other logs besides the sonar.log

I saw a note somewhere about increasing the memory for the elasticsearch process, which I tried but that simply cause the startup process to fail:

jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/staples/sonar/sonarqube-6.7.3/temp
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/staples/sonar/sonarqube-6.7.3/elasticsearch]: /opt/staples/sonar/sonarqube-6.7.3/elasticsearch/bin/elasticsearch -Epath.conf=/opt/staples/sonar/sonarqube-6.7.3/temp/conf/es
jvm 1    | 2018.07.03 03:35:14 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.e.p.PluginsService] no modules loaded
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1    | Error: Could not find or load main class #
jvm 1    | 2018.07.03 03:35:15 WARN  app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1    | 2018.07.03 03:35:15 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Again, there are no logs other than the sonar.log.

As a side note, I had this up and running at one point, and it stopped working with the above issues, so I reinstalled SonarQube but the startup issue remains.


(G Ann Campbell) #2

Hi,

It’s rather odd that there are no other files in your logs directory. It makes me wonder if the process has recursive write permissions to $SONARQUBE_HOME…?

Ann