Error restarting Confluence after trying to upgrade to 8.57 LTS

[vipulmishra]

We have a running version of Confluence server (on-prem) version 8.56 LTS. After today's security advisory, we tried to upgrade it to version 8.57 LTS. After upgrade Conluence would not start and complains of expired license. We tried to rollback to our previous version of 8.56 but even that is not able to start and complains of expired version. Please help.

[bluesource Atlassian ORG]

so, just to get it right:

Atlassian releases 8.5.7 LTS on 05-Mar-2024 but all Server Licenses went OOL on 14-Feb-2024

the download site (https://www.atlassian.com/software/confluence/download-archives) says:

"If you’d like to continue using a Server license, you can upgrade to the Confluence 8.5 Long Term Support release or earlier."

nevertheless 8.5.7 LTS does not work.

sorry, but this is ridiculous.

Either you provide support for security issues, or you leave it.

[Aaron Pavez _ServiceRocket_]

Hi @bluesource Atlassian ORG @vipulmishra 

Confluence 8.5.x will be the last version supporting Server licenses.

If this is an issue with the license, try getting a new trial license in my.atlassian.com, that way you can at least use your confluence instance.

You can manually change the license:

https://confluence.atlassian.com/confkb/how-to-change-the-confluence-license-in-confluence-cfg-xml-file-720405151.html

It would also help us if you could share a screenshot of the whole screen with the error.

- You could also check when your license expired under my.atlassian.com. If is still active, reach out to Atlassian.

Hope this helps!

Regards

[bluesource Atlassian ORG]

Hi Aaron,

_Every_ Atlassian Confluence Server License in this world expired at 15-Feb-2024. You cannot get a new trial License for Server via my.atlassian.com cause its EOL as anncounced from Atlassian itself (see https://www.atlassian.com/migration/assess/journey-to-cloud)

My only question is: Why does Atlassian release a server version 8.5.7 LTS on 05-Mar-2024, if there is no Confluence Server instance in this world for supporting this release...

is this a joke or something? :)

[Fabio Racobaldo _Herzum_]

Hi @vipulmishra ,

if your license is expired you can't start a upgraded version. You need to perform a rollback to Confluence 8.5.6 version. 

As workaround you can buy a new license and apply it into the upgraded jira instance as specified here https://confluence.atlassian.com/confkb/how-to-change-the-confluence-license-in-confluence-cfg-xml-720405151.html

Hope this helps,

Fabio

[Benjamin]

Hi @vipulmishra ,

When did your license expired? It should have still work on 8.5.6 if you had no issues there.

How did you rollback to 8.5.6? 

[vipulmishra]

rollback the database first and then rollback from the backup we did at the beginning of upgrade.

[Benjamin]

How did you rollback actually? Did you just reinstall 8.5.6 and just dump the backup database from 8.5.6 back?

You may want to see if you can go one more version back if you can. Meaning the version you had before 8.5.6.

Would recommend doing this all on a dev instance first. 

[vipulmishra]

this is what I see in the logs - 2024-03-19 14:42:14,515 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
2024-03-19 14:42:16,630 ERROR [Caesium-1-3] [troubleshooting.healthcheck.concurrent.SupportHealthCheckProcess] lambda$getCompletedStatuses$0 Health check 'License Expiry' failed with severity 'major': 'Your maintenance period expired on 14 Feb 2024. Renew your license to be eligible for support and product upgrades.'

[Benjamin]

Strange. should have been able to go back to the previous version that was working with your license. 

You may want to go back one more version as mentioned or buy a new license as @Fabio Racobaldo _Herzum_ mentioned.

Keep in mind. Server has sunsetted. It will beneficial to move to DC or cloud to keep your system supported and up to date for security vulnerabilities.

[Joseph Maxwell]

Hi @vipulmishra @bluesource Atlassian ORG

Did Atlassian ever resolve this issue? As it seems to be a mistake on their behalf. We have the same problem.

[Dimitris Moraitidis]

I tried upgrading yesterday from .6 to .7 and I received the license error. Rolled back and it worked again.