nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira upgrade from 6.4 to 7.3

Jason Chuang

Last year, I upgraded from Jira 6.4 to 7.3, and probably missing something, it displays the following at the top of each page:

***********************************
JIRA Software is currently unavailable. This might be because an upgrade task has failed to run or has not yet completed.

Please contact your system administrator if you continue to see this message.

***********************************

I'm with MySQL 5.7.x on Windows platform, would like to upgrade to the latest version Jira 7.11.

Should I upgrade by using the procedure of 7.3 to 7.11, or should I fix this problem first?

Accepted answers

AhmadDanial

Hi there.

Let us try to troubleshoot the problem first before upgrading since the upgrade might not necessarily fix the issue. Since we do not have visibility on your atlassian-jira.log so far, I do not have context on the possible root cause of it yet, though a quick search yields the following KB:

"JIRA Software is currently unavailable" error after upgrading to JIRA 7 or newer

Perhaps you can go through the atlassian-jira.log first so we can verify if that is the case before implementing the solution? Thanks.

All comments

AhmadDanial

Hi there.

"JIRA Software is currently unavailable" error after upgrading to JIRA 7 or newer

Perhaps you can go through the atlassian-jira.log first so we can verify if that is the case before implementing the solution? Thanks.

Jason Chuang

The following error is found from atlassian-jira.log.

2018-08-06 18:44:01,775 active-objects-init-JiraTenantImpl{id='system'}-0 DEBUG anonymous [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.plugins.authentication.atlassian-authentication-plugin] created ActiveObjects
2018-08-06 18:44:01,791 active-objects-init-JiraTenantImpl{id='system'}-0 DEBUG anonymous [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.streams.thirdparty-plugin] creating ActiveObjects
2018-08-06 18:44:02,477 active-objects-init-JiraTenantImpl{id='system'}-0 DEBUG anonymous [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.streams.thirdparty-plugin] created ActiveObjects
2018-08-06 18:44:04,630 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.pyxis.greenhopper.jira]
2018-08-06 18:44:04,786 JIRA-Bootstrap ERROR [c.a.s.core.upgrade.PluginUpgrader] Upgrade failed: This version of JIRA Agile requires a minimum build number of #45 in order to proceed. The latest upgrade task to have been successfully completed is #42. You must uninstall this version of JIRA Agile and attempt an upgrade via an intermediary version.
java.lang.IllegalStateException: This version of JIRA Agile requires a minimum build number of #45 in order to proceed. The latest upgrade task to have been successfully completed is #42. You must uninstall this version of JIRA Agile and attempt an upgrade via an intermediary version.
 at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.checkMinimumDataRequirement(AbstractGhUpgradeTask.java:85)
 at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.doUpgrade(AbstractGhUpgradeTask.java:44)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
 at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
 at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
 at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
 at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
 at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
 at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
 at com.sun.proxy.$Proxy817.doUpgrade(Unknown Source)
 at com.atlassian.sal.core.upgrade.PluginUpgrader.doUpgrade(PluginUpgrader.java:72)
 at com.atlassian.sal.core.upgrade.PluginUpgrader.upgrade(PluginUpgrader.java:57)
 at com.atlassian.sal.core.upgrade.DefaultPluginUpgradeManager$1.doInTransaction(DefaultPluginUpgradeManager.java:198)
 at com.atlassian.sal.core.upgrade.DefaultPluginUpgradeManager$1.doInTransaction(DefaultPluginUpgradeManager.java:173)
 at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:21)
 at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34)
 ... 2 filtered
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
 at com.sun.proxy.$Proxy56.doInTransaction(Unknown Source)
 ... 2 filtered
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136)
 at com.sun.proxy.$Proxy56.doInTransaction(Unknown Source)
 at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:18)
 at com.atlassian.sal.core.upgrade.DefaultPluginUpgradeManager.upgradePlugin(DefaultPluginUpgradeManager.java:173)
 at com.atlassian.sal.core.upgrade.DefaultPluginUpgradeManager.upgradeInternal(DefaultPluginUpgradeManager.java:152)
 at com.atlassian.sal.jira.upgrade.JiraPluginUpgradeManager.upgradeInternal(JiraPluginUpgradeManager.java:49)
 at com.atlassian.sal.core.upgrade.DefaultPluginUpgradeManager.upgrade(DefaultPluginUpgradeManager.java:136)

any procedure should I perform to get it right.

As my database is with MySQL 5.7 and JIRA 7.3.6 now, seems there is no way to downgrade and perform upgrade from JIRA 7.0.

Thanks for your guidance in advance.

AhmadDanial

Hi, Jason.

Thank you for the log snippet. Interesting enough, the Jira Agile ERROR that we are seeing relates to a different KB that we came across here - This version of JIRA Agile requires a minimum build number of #45 in order to proceed which is related to the following bug:

JSWSERVER-12792: Importing from Server to Cloud or Upgrading to JIRA 7.1.0 from Agile earlier than build 45 is causing errors

As of now, may I suggest you to proceed to generate a backup (Very important) before you proceed to perform the workaround in the KB here first before we look into the other KB related to the "JIRA Software is currently unavailable"?

The reason why I am asking for this is because we do not see the error so far in the atlassian-jira.log as what we would expect:

java.lang.ClassCastException: com.pyxis.greenhopper.jira.fields.NotSupported cannot be cast to com.pyxis.greenhopper.jira.fields.CustomIssueField

Please let me know your thoughts on this. Thank you.

Jason Chuang

Hi Ahmad,

My JIRA is working now by performing the workaround of that KB, the error is gone and I performed the following to have the latest version of JIRA.

installed clean copy of JIRA 7.11.1 on another server.
backup system of JIRA 7.3.6 from old server with attachment.
restored the backup of 7.3.6 and copy attachment to 7.11.1.

My problem is resolved, thanks a lot for your help, cheers.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

upgrade