Jira Data Center node will not start due to restricted access to $SHARED_HOME

お困りですか?

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

コミュニティに質問


プラットフォームについて: Data Center のみ - この記事は、Data Center プラットフォームのアトラシアン製品にのみ適用されます。

この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。

*Fisheye および Crucible は除く

要約

Starting a new or restarting existing Jira Data Center node appears unresponsive for a long time.

環境

Any Jira Data Center version, Linux or Windows platform.

診断

$JIRA_HOME/log/atlassian-jira.log* will show exceptions like below on a startup attempt:

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\atlassian-client-resource-4.22.4-REL-0001.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\atlassian-pocketknife-api-commons-plugin-1.0.7.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\atlassian-timed-promise-plugin-4.22.4-REL-0001.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\incident-management-plugin-4.22.4-REL-0001.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-assets-plugin-4.22.4-REL-0001.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-monitor-plugin-8.22.1.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-monitor-plugin-8.22.2.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-monitor-plugin-8.22.4.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-plugin-8.22.1.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-plugin-8.22.2.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-software-plugin-8.22.4.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-transition-triggers-plugin-8.22.2.jar

com.atlassian.plugin.PluginParseException: Cannot open JAR file: \\yourfileserver\Shares\Jira\plugins\installed-plugins\jira-workinghours-plugin-4.22.4-REL-0001.jar

Where \\yourfileserver\Shares\Jira would correspond to the $SHARED_HOME drive in your Jira Data Center configuration.

In most cases the 'caused by' statement in the exception will be:

Caused by: java.io.IOException: The specified network name is no longer available


If the above errors show up in the logs, we recommend performing system level troubleshooting  such as verifying that the server has full and unrestricted access to the $SHARED_HOME drive.

This would include network level as well the file server level troubleshooting, for example:

  • Ping the file server hosting the $SHARED_HOME drive continuously (i.e. 'ping -t') from the Jira server itself to verify there is no packet loss.
  • Copy all the .jar files from the $SHARED_HOME/installed-plugins folder to a local drive and then perform a binary comparison (diff on Linux, fc /b on Windows) of the 'source' and 'target' files - were the files copied successfully and the comparison operations check out?
  • Perform a write operation to the $SHARED_HOME folder

(i) For the file system level troubleshooting, please also verify you're logged in to the Jira server with the same user account that is configured to run Jira as it could as well be a file permission issue (though in case of file permissions  'access denied' errors in the logs are usually evident, still worth double checking)

原因

The most likely cause is due to the environment: something is holding Java from reading the Jira plugins from $SHARED_HOME/plugins/installed-plugins folder consistently. It could be due to a genuine random network issue, or could be an Antivirus on the file server preventing access to the files.

In the above example, the root cause was that an Anti-virus on the file server for some reason marked the .jar files as malware. In this scenario, even though the share and files seemingly appeared as available, the Antivirus prevented Jira nodes from accessing the files, resulting in the Jira startup failure. We were able to identify that there was indeed something preventing the files from being accessed properly when we tried to actually copy the files from the shared home to destination

Certain Anti-virus programs are known to clash with Jira and will either need to be disabled, or configure exceptions on the Jira directories:

ソリューション

Resolve any underlying network, Antivirus, or file server issue. Once resolved, restart Jira.


最終更新日 2023 年 6 月 6 日

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

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