SonarQube exits with 143
I am trying to Setup SonarQube on Centos 6 VM with 6GB of RAM. The process always exits with 143.
On analysis I found that the JVM is being sent a SIGTERM signal and thus exiting. There are no core dumps and dmesg is also quite unhelpful. I also tried fiddling with the Memory options to no avail.
If some can help me debug this issue it will be quite useful. At least, I will have some idea why this software is being terminated.
jvm 1 | 2018.03.06 15:32:59 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2018.03.06 15:32:59 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | 2018.03.06 15:33:07 INFO app[][o.s.a.SchedulerImpl] Process[es] is up
jvm 1 | 2018.03.06 15:33:07 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [/home/sonar/sonar/sonarqube-7.0]: /opt/jdk1.8.0_161/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/home/sonar/sonar/sonarqube-7.0/temp -Xrs -Xmx4g -Xms4g -XX:+HeapDumpOnOutOfMemoryError -cp ./lib/common/*:./lib/server/*:/home/sonar/sonar/sonarqube-7.0/lib/jdbc/mysql/mysql-connector-java-5.1.42.jar org.sonar.server.app.WebServer /home/sonar/sonar/sonarqube-7.0/temp/sq-process3024208901604150849properties
jvm 1 | 2018.03.06 15:33:12 INFO app[][o.s.a.SchedulerImpl] Process [web] is stopped
jvm 1 | 2018.03.06 15:33:12 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1 | 2018.03.06 15:33:12 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143
jvm 1 | 2018.03.06 15:33:12 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
wrapper | <-- Wrapper Stopped
Answer
I have been experiencing this as well, but I managed to cure it this morning.
For me, the problem was not bad Elastic system configuration, invalid database credentials, and it was not killed by the OOM killer. For me the problem was that we had the "sonar-cfamily-plugin-5.1.10083.jar" in the extensions/plugins folder, but we did not have a license to use it (we are a Java shop, I doubt anyone even tried to run it). In SonarQube 6.6, we got warnings about it being unlicensed, but nothing crashed. In 6.7, as well as 6.7.3 and 7.0, es crashed with 143 (I believe we still got the warning, but since it was in our 6.6 logs I didn't consider it to be a problem.)
I figured this out because I tried a 'super clean' install (no plugins) and SonarQube 7.0 stayed up; adding the plugins back, es crashed with 143. CFamily was the first plugin I tried to remove (since we don't really use it) and SonarQube stayed up.
I haven't gone back to 6.7 to see if removing an unlicenses cfamily plugin clears up the ES 143 exit there as well, but if you are experiencing this maddening error and none of the other suggestions apply to you, this might be something to look at. At least, something to try would be to remove all your plugins and see if SonarQube starts correctly; then one by one add them back until you find the one that introduces the ES 143 exit problem.