SonarQube 6.7 failed to start because CONFIG_SECCOMP not compiled into kernel

Question

I've just upgraded SonarQube from 6.0 to 6.7 LTS running in a CentOS 6 box, and noticed that ElasticSearch (ES) failed to start because the kernel (2.6.32-696.3.1.el6.x86_64) doesn't have seccomp available.

This is officially documented at System call filter check and a correct workaround for systems without this feature is to configure bootstrap.system_call_filter to false in elasticsearch.yml.

The issue here is because Sonar creates the ES configuration at startup, writing in $SONAR_HOME/temp/conf/es/elasticsearch.yml and I haven't found a way to set bootstrap.system_call_filter property.

I tried a natural (undocumented) way introducing sonar.search.bootstrap.system_call_filter and bootstrap.system_call_filter properties in sonar.properties but it doesn't work.

Answer 1

We had the same problem. At first we used the above solution but after searching in the sonar code on github found the place where this setting should be placed:

Edit the sonar.properties file and change the line:

#sonar.search.javaAdditionalOpts=

to

sonar.search.javaAdditionalOpts=-Dbootstrap.system_call_filter=false

Answer 2

For sonarqube docker image, setup additional environment to disable this feature when "docker run":

-e SONAR_SEARCH_JAVAADDITIONALOPTS="-Dbootstrap.system_call_filter=false"