SonarQube not starting with Elasticsearch issue

Hey there.

My guess is that some system administrator (or an automated tool) went and wiped Log4J from your server – which has the effect of not letting Elasticsearch (and therefore SonarQube) start.

We’ve confirmed that the minimum supported version of SonarQube (v8.9 LTS) is not vulnerable to the infamous Log4Shell vulnerability (SonarQube, SonarCloud, and the Log4J vulnerability).

  • You could try reinstalling your existing version of SonarQube
  • Immediately work on an upgrade to the minimum supported version of SonarQube, v8.9 LTS, which also includes a newer version of Elasticsearch (and the underlying Log4J) less likely to trigger cleanup.
1 Like