SonarQube DE 8.0 failed to start

Hi, there!

I faced the problem on the setup of SonarQube 8 Developer Edition.
Here are the details:

2019.10.25 10:45:55 INFO  web[][o.s.p.ProcessEntryPoint] Starting web
2019.10.25 10:45:56 INFO  web[][o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read
2019.10.25 10:45:56 INFO  web[][o.s.c.e.CoreExtensionsLoader] Loaded core extensions: developer-edition, developer-scanner, developer-server, license
2019.10.25 10:45:56 INFO  web[][o.e.p.PluginsService] no modules loaded
2019.10.25 10:45:56 INFO  web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.join.ParentJoinPlugin]
2019.10.25 10:45:56 INFO  web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.percolator.PercolatorPlugin]
2019.10.25 10:45:56 INFO  web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.10.25 10:45:57 INFO  web[][o.s.s.e.EsClientProvider] Connected to local Elasticsearch: []
2019.10.25 10:45:57 INFO  web[][o.s.s.p.LogServerVersion] SonarQube Server / / f869d840f12a4dfa69533e17d3b27558617a7f82
2019.10.25 10:45:57 INFO  web[][o.sonar.db.Database] Create JDBC data source for jdbc:postgresql://
2019.10.25 10:45:58 INFO  web[][o.s.s.p.ServerFileSystemImpl] SonarQube home: /opt/sonarqube
2019.10.25 10:45:58 INFO  web[][o.s.s.u.SystemPasscodeImpl] System authentication by passcode is disabled
2019.10.25 10:45:58 ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly.
2019.10.25 10:45:59 INFO  web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000
2019.10.25 10:45:59 INFO  web[][o.s.p.ProcessEntryPoint] Hard stopping process

Is it related to SQ’s internals (Tomcat version), or the fault is on my side?


Welcome to the community!

Here’s the pertinent part of your log:

It sounds like you’re trying to upgrade from a version that’s older than 7.9. You can upgrade across multiple versions, but you can’t skip any LTSs in the middle.


Hi, Ann!

Thank you for your reply.
But, I didn’t upgrade from previous version. What I do is download a binary at
into Docker image, which later is used for new instance of SonarQube.

Here are some details, of the build context, related to SonarQube setup.


FROM .../base/debian10:slim


ENV JAVA_HOME /opt/java/jdk-${JAVA_VER}

RUN  curl -fSsL ${JAVA_URL} --output java.tgz && \
    tar -xzf java.tgz --directory /opt/java/ && rm -f java.tgz

# Some Ansible stuff
- name: BUILD | Get SonarQube binary
  become: true
    src: '{{ item }}.zip'
    dest: /opt
    mode: '0755'
    group: sonarqube
    owner: sonarqube
    remote_src: yes
    - '{{ }}-{{ sonar_version }}'
    - '{{ binaries.scan }}'

After the image is built, next, ‘docker-compose’ brings SonarQube server up from that image.


Can you verify that there’s not an overlooked old sonar or sonarqube schema in the database you’re pointing the docker image to? Because that’s what the error you’re getting indicates: the database has already been used with an old version of SonarQube.


Hi, Ann!

Yes, there’s. And you were right – once I fixed older schema, SQ server is up and running.
Thanks a lot!