Bitbucket Server does not start - Unable to start the following plugins due to timeout while waiting for plugin to enable

お困りですか?

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

コミュニティに質問

プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

問題

Bitbucket Server does not start.

The following appears in the atlassian-bitbucket.log

2016-02-08 12:26:08,992 ERROR [spring-startup]  c.a.plugin.manager.PluginEnabler Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.bitbucket.bitbucket-branch-utils,com.atlassian.plugins.atlassian-nav-links-plugin,com.atlassian.bitbucket.bitbucket-dev-summary-plugin,org.tmatesoft.subgit.bitbucket-svn-importer,com.atlassian.plugins.atlassian-remote-event-common-plugin,com.atlassian.bitbucket.bitbucket-jira-integration,com.atlassian.plugins.atlassian-remote-event-producer-plugin,com.atlassian.upm.atlassian-universal-plugin-manager-plugin,com.atlassian.plugins.atlassian-remote-event-consumer-plugin

原因

As the Bitbucket Server application starts up, it loads the installed plugins from the available ones.

This is a fairly resource intensive process and can place a sizeable load on the I/O of the disk and CPU of the machine that is hosting the Bitbucket Server application instance.

If the required resources aren't available, the plugins may timeout and cause the application to be left in an unusable state.

The default timeout value is 300 seconds.


回避策

It is possible to increase the plugin timeout period. To do this, add the the following argument to file:

  • $BITBUCKET_INSTALLATION/bin/_start-webapp.sh

Locate the line starting with JVM_SUPPORT_RECOMMENDED_ARGS and remove any leading hash character (#) if there is one. Add the following in between the double quotes on that line:

-Datlassian.plugins.enable.wait=360

That section should now look like:

JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.plugins.enable.wait=360"

This increases the timeout value to 360 seconds.


This may increase the time taken to start the Bitbucket Server application up, and it does address the symptom rather than the root cause. If the machine is not powerful enough to run the application, we would suggest looking at upgrading to a more powerful host.


ソリューション

Ensure the machine meets minimum requirements and has enough memory, CPU, and disk I/O available.

最終更新日: 2019 年 10 月 10 日

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

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