License Too Old For Build: We found a problem with your JIRA license
Your current Jira Software license doesn't allow you to upgrade to this version of JIRA (8.8.1). Jira Software expired on 21/May/20 2:00 PM, and you can currently only upgrade to versions released prior to this date. Alternatively you can renew your license at my.atlassian.com which will allow you to upgrade to this version of JIRA (8.8.1). You can enter your new license here.
See our documentation for more information on licensing errors.
According to https://confluence.atlassian.com/jirasoftware/jira-software-8-8-x-release-notes-994314852.html, 8.8.1 is released on March 19th, 2020 - 2 months before my license expired. I am still getting above error. Current database build number is 808001. Which means, I must use 8.8.1 or higher. But it is not working! :(
same here... trying to upgrade from 7.13.0 to 8.5.5.
License has expired 29 June 2020.
Release date 8.5.5: 8 June 2020
We're currently in the process of migrating a "standalone" JIRA Software instance into company central JIRA environment - that's why we didn't renew the license for that legacy instance.
Current 7.13.0 version is running in Kubernetes using atlassian/jira-software:7.13.0 image.
Upgrading to any version between 8.5.0 and 8.5.5 failed with above mentioned error msg.
Maybe it's worth mentioning that the system is running on Developer License.
Hi,
we had exactly the same issue. We were trying to install a version that was actually released after our expiration date (8.11.0), which obviously failed with the above error message.
However after trying to revert to 8.9.0, we still received the exact same error message, even if 8.9.0 was before our expiration date.
Luckily we did a backup of our JIRA home folder before. After replacing the existing home folder with the backup, JIRA started working again.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It didn't work for me. I have JIRA hosted in docker container. I simply reused the mounted JIRA volumes to redeploy JIRA on another system (this is equivalent of 'replacing home folder with backup').
I am glad to see it worked for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @mandaarp ,
To provide a little more clarity on how the licenses work - you can install any version that has a build date before the date of your license's maintenance expiration. For Jira 8.8.1, that build date is April 22, 2020. The March date you noted was for the release of 8.8.0 - subsequent bugfix releases (like 8.8.1) need to be within your maintenance period as well for the upgrade to work.
Although it seems unlike to be a problem, what's the current date and timezone of the operating system on the server you're trying to upgrade on? We've had edge cases in the past where an unexpected date format has caused the expiration checker to fail and I'd like to rule that out.
Thanks,
Daniel | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like build date for JIRA 8.8.1 (April 22nd, 2020) is well before my license expiration (May 21st, 2020). Why is it not working then?
Here is the output of date command on server:
> date
Wed Jul 22 21:49:50 PDT 2020
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @mandaarp - I've been poking around on your license a bit and it seems to work in our test environment with an 8.8.1 server without issue. I'm hoping now to determine if perhaps there was an older license applied to your instance in the past that is tripping the license check up.
Would you be able to run this database query:
SELECT count(*) FROM productlicense;
We would expect this to return 1; if it comes back with 2 or more, then the incorrect licenses need to be removed from the database and Jira restarted. Just running "SELECT *" instead of count(*) will return the actual rows for your inspection - depending on your database client you could delete extraneous rows from the GUI or use a DELETE statement targeted at extra rows.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Daniel Eads I ran the query and result was 1. I also checked the 'license' text value in productlicense table and it is exactly same as the one in https://my.atlassian.com/product.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From ${JIRA_HOME}/log/atlassian-jira.log:
___ Plugin System Started _________________
2020-07-25 08:46:55,828+0000 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We found a problem with your JIRA license
2020-07-25 08:46:55,829+0000 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] Your current Jira Software license doesn't allow you to upgrade to this version of JIRA (8.8.1). Jira Software expired on 21/May/20 2:00 PM, and you can currently only upgrade to versions released prior to this date. Alternatively you can renew your license at my.atlassian.com (http://my.atlassian.com) which will allow you to upgrade to this version of JIRA (8.8.1). You can enter your new license here (/secure/ConfirmNewInstallationWithOldLicense!default.jspa).
See our documentation for more information on licensing errors.
2020-07-25 08:46:55,829+0000 JIRA-Bootstrap ERROR [c.a.jira.upgrade.UpgradeLauncher] No upgrade is being performed due to detected inconsistencies. We found a problem with your JIRA license
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @mandaarp
When did you start your upgrade? If your license expired back in May and did the upgrade recently it might be why that message is being displayed. I presume your Jira version is before 8.8.1?
I believe the checks are done on date you perform the upgrade rather than when the version itself was released but maybe someone from Atlassian can confirm.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I must have upgraded to 8.8.1 before the license expiration (May 21st, 2020). Otherwise, JIRA wouldn't allow to upgrade with expired license.
Yeah, I am waiting for someone for Atlassian to resolve this weird issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.