search

Oteemo / charts

Helm chart repository
https://oteemo.github.io/charts
MIT License
181 stars 234 forks source link

Sonarqube : ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly #259

Open MrAmbiG opened 3 years ago

MrAmbiG commented 3 years ago

version: latest as of today [19/2/2021] database: external postgresql logs 2021.02.18 18:27:19 INFO web[][o.s.s.p.ServerFileSystemImpl] SonarQube home: /opt/sonarqube 2021.02.18 18:27:19 INFO web[][o.s.s.u.SystemPasscodeImpl] System authentication by passcode is disabled 2021.02.18 18:27:19 ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly. 2021.02.18 18:27:19 INFO web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000 2021.02.18 18:27:19 INFO web[][o.s.p.ProcessEntryPoint] Hard stopping process 2021.02.18 18:27:20 INFO app[][o.s.a.SchedulerImpl] Process[web] is stopped 2021.02.18 18:27:20 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [es]: 143 2021.02.18 18:27:20 INFO app[][o.s.a.SchedulerImpl] Process[es] is stopped 2021.02.18 18:27:20 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped

steffbeckers commented 3 years ago

Same issue here. Is there any progress on this?

Mikaciu commented 2 years ago

Hello,

I'm guessing you're using SQ 8.6, 8.7 released on 2021-02-25. What edition is this ?

I would advise you to change the image.tag value to 8.9-community (or 8.9-<edition> if you're not using community) if you are able to do so, it may solve your issue.

HTH

Alex-z76 commented 2 years ago

I've tried with image.tag with value 8.9-community, and lts-community. However, I keep getting the same error. Any suggestion on that?

2021.08.04 08:21:13 ERROR web[][o.s.s.p.PlatformImpl] Web server startup failed: Current version is too old. Please upgrade to Long Term Support version firstly.
2021.08.04 08:21:13 INFO  web[][o.s.s.a.EmbeddedTomcat] HTTP connector enabled on port 9000

Thanks

amit-k-yadav commented 2 years ago

@Alex-z76 I am not sure which version you are currently using but as per the docs, this happens when you try to upgrade to a Major Version Number.

Below are some Migration Path Examples:

Example 1 – From 8.1 > 9.0, the migration path is 8.1 > 8.9.1 LTS > 9.0 Example 2 – From 8.2 > 8.9 LTS, the migration path is 8.2 > the latest 8.9 LTS patch. Example 3 – From 6.7.7 LTS > 8.9 LTS, the migration path is 6.7.7 LTS > 7.9.6 LTS > the latest 8.9 LTS patch.

I suppose your case is similar to "Example 1" and you need to follow the below steps:

  1. Backup your Database
  2. Change the tag to 8.9-community and upgrade your release (using helm upgrade)
  3. Once the new pod is started, go to http://yourSonarQubeServerURL you should see something like "SonarQube is under maintenance"
  4. Browse to http://yourSonarQubeServerURL/setup and follow the setup instructions (upgrade the Database)
  5. Now that you're on 8.9-community version you can change the tag to 9.0.1-community and upgrade your release. Once the new pod starts running, repeat steps 1, 3, and 4.

This worked for me to go from 8.4 to 9.0.1, I hope it helps you.

See Upgrade the Server guide for more details.

Alex-z76 commented 2 years ago

Hi @amit-k-yadav , thanks for your reply.

I have a Bitnami Postgres-HA with 2 instances deployed to my K8s cluster, with three ClusterIP Services. I'm trying to persist SonarQube data to this HA database instance through its PgPool service as using the other two services might connect and try to write to the read-only node in my pool.

Using Oteemo's SonarQube chart, I configure the values to use my own Postgres-HA database below.

# Persistence
postgresql:
  enabled: false
  postgresqlServer: "myservice-postgresql-ha-pgpool.my-namespace"
  postgresqlUsername: "MyPostgresUsername"
  postgresqlPassword: "MyPostgresPassword"
  postgresqlDatabase: "mysonardb"

  persistence:
    enabled: false

The service for the pgpool points/labels to my pgpool pod, the other two services labels to both Postgres instance pods. Trying to connect to the services that point to the instance direct works, but from time to time, I get ERROR: cannot execute INSERT in a read-only transaction, which is fine, as it means SonarQube is connecting through the service and the service load-balance to the read-only node. However, using their provided PgPool service, I avoid this error. But I get the error of this GitHub issue.

Now, I'm not sure if the issue is with SonarQube or the version of PostgreSQL it supports.

Do you have any idea or know a workaround or a solution for that?

Thanks!