Import from Cloud to Standalone: Failed to start JIRA due to a build number inconsistency

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

atlassian-jira.log に次のメッセージが表示される。

****************************************************************************************************
Failed to start JIRA due to a build number inconsistency.
The data present in your database is newer than the version of JIRA you are trying to startup.
Database version is: 64014
JIRA app version is: 6346
Please use the correct version of JIRA. You are running: 6.3.15#6346-sha1:dbc023dd75cecacf443c4b235f66124b15f5c5fe
****************************************************************************************************

診断

When importing a JIRA Cloud instance into a JIRA Standalone instance, on occasion this error is presented.

原因

The cause of this error is still under investigation.

回避策

The solution to this error appears to be increasing the available memory to JIRA by increasing JVM Heap Size and Swap Space according to the JIRA Sizing Guide, since the size of JIRA instances can vary. Please refer to Increasing JIRA Memory for the steps to increase the heap size.

最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.