Sonarqube developer edition wont start from installing

es.txt (184.8 KB) sonar.txt (428.5 KB) web.txt (96.2 KB)

Java version: openjdk version “11.0.5”
PostgreSQL version: PostgreSQL 9.2.24 on x86_64-redhat-linux-gnu

I am Trying to setup SQ (Developer edition) with postgreSQL as the database. However, I am not getting any luck getting it to start. Keeps failing. I have attached the log files, any help would be much appreciated!!!


this is ES related, your sonar.log has:

2019.11.04 09:20:29 WARN app[o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143

Did you consider the hints here => for
Linux (don’t run as root … etc.) ?
Also for diagnostics you should increase the loglevel to DEBUG to get more details via
$SONARQUBE_HOME/conf/ => set or even for all
logs with sonar.log.level=DEBUG


yup, everything is exact with the link you suggested, and I have sonar.log.level=TRACE
still cant find why its not working

yes you had loglevel trace already, missed that.
There are a lot of similar threads for es exit code 143, check

i noticed a failed to connect to node error…how would I go abouts fixing that?

Is this the pure release version, or are there addtional plugins in $SONARQUBE_HOME/extensions ?
Did you change any of the default jvm parameters in …/conf/ ?
stop SQ
delete $SONARQUBE_HOME/data/es6 Folder
change config to use the builtin H2 database
start SQ
to make sure it’s not db related

this is what is in the plugins, but this was straight from the zip file I downloaded in the link for the SQ version (Developer edition).

With regards to my, it is attached (20.0 KB)

When you say change it back to the buitin H2 database, how do I do that? just comment out my psotgressql info and leave it as is?

OK, so no additional plugins.
I can’t find anything suspicious in your, but i would increase the heapspace for
ES process, Xms has to be equal to Xmx. e.g. :

# JVM options of Elasticsearch process -Xms2G -XX:+HeapDumpOnOutOfMemoryError

To test with the builtin H2 db, simply deactivate your db properties:
sonar.jdbc.username, sonar.jdbc.password, sonar.jdbc.url

I noticed this error, failed to connect to a node? would that mean I have a port issue?
This is after deleting the es6 and setting it back to the H2 database…same errors as before :confused:

Does the user that runs Sonarqube has sufficient rights for $SONARQUBE_HOME/data folder ?
Maybe it’s a port issue or some process is lurking in the background.

you may try

# Elasticsearch port. Default is 9001. Use 0 to get a free port.
# As a security precaution, should be blocked by a firewall and not exposed to the Internet.

so i changed it to 0, and the user has rights to that folder, yet still failed to connect to node

Hi guys,

The web log includes this:

2019.11.04 09:20:29 ERROR web[o.s.s.p.Platform] Web server startup failed
java.lang.IllegalStateException: Fail to connect to database

Caused by: org.sonar.api.utils.MessageException: Unsupported postgresql version: 9.2. Minimal supported version is 9.3.

(I looked in the web log after my text search of the other two logs failed to find the string “ERROR”.)


Hi Ann,

OK, missed that even so i’ve searched the logs :frowning:
But what about the same ES error after switching to the builtin H2 database !?


Hi Gilbert,

… I’d want to see the logs on that. If it truly failed to connect to the H2 database, then I’d suspect some overly vigilant process on the box blocking access to the necessary ports.


Hi Ann,

after rechecking my logs (SQ Enterprise 7.9.1 / 8.0, running on windows server 2016), it seems this
ES connection refused … errors are quite ‘normal’. Found a bunch ot those entries in ES logs, but everything works just fine.

@devine to get back on track we’ll need to check the logs of your test with builtin H2 database.

btw, with all those (similar) postings, it seems a lot of users have problems with Sonarqube setup,
especially on Linux systems - even when the documentation gets constantly better.
What about providing a wizard driven installer for windows/linux … , doing all that nasty stuff ?
It could also check whether prerequisites are fulfilled and ask for basic properties (SQ server base url,
mail server settings …) ?


Fixed the issue, Wrong postgresql installed, upgraded to postgres 11 and restarted SQ and now it works fine

Finally, congratulations :sweat_smile:


To add on to this, when ever a PR is committed…And i go to review the PR on bitbucket, it does not show the decoration, yet on SQ, it has the report visible with a link to view the PR on bitbucket…any ideas as to why ??

Hi @devine,

you should create a new thread, as this is not relevant to your original problem.