Problem with SonarQube start on Ubuntu 1604. Process exited with exit value [es]: 143

SonarQube
10

Hi Pavel,

Actually this is only a warning, so it’s not fatal. And in fact you do get a successful startup log afterwards:

2018.06.19 06:25:21 INFO  es[][o.e.n.Node] started

All in all I would suggest you focus on this external signal SonarQube seems to be receiving (from your original post):

2018.06.19 17:33:59 INFO  app[][o.s.a.SchedulerImpl] Stopping SonarQube
JVM exited normally.
Signal trapped.  Details:
  signal number=17 (SIGCHLD), source="unknown"
Received SIGCHLD, checking JVM process status.
JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
2018.06.19 17:33:59 WARN  app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 143

If you didn’t kill the process on purpose, then the OS might have, for reasons you need to discover. One starting point could be to look at the CPU/RAM state of your machine as SonarQube starts-up, and see if anything stands out (or if there’s any resource starvation anywhere). You should also double-check/correlate with the actual JVM settings you’ve defined in sonar.properties.

1 Like