Bamboo fails to start with "Error occurred while starting Plugin Manager"
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Bamboo fails to start up. The logs (specifically atlassian-jira.log) shows errors similar to the following:
2022-06-24 07:58:49,373 FATAL \[localhost-startStop-1] \[UpgradeLauncher] Failed to initialise Bamboo container
com.atlassian.bamboo.configuration.ConfigurationException: Failed to start Bamboo
at com.atlassian.bamboo.upgrade.UpgradeLauncher.initialiseBambooContainer(UpgradeLauncher.java:184\)
at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(UpgradeLauncher.java:105\)
at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:52\)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4763\)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5232\)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183\)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1427\)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1417\)
at java.util.concurrent.FutureTask.run(FutureTask.java:266\)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149\)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624\)
at java.lang.Thread.run(Thread.java:748\)
Caused by: java.lang.IllegalArgumentException: The plugin key 'my.bamboo-plugin' must either match the OSGi bundle symbolic name \(Bundle-SymbolicName\) or be specified in the Atlassian-Plugin-Key manifest header
at com.atlassian.plugin.osgi.factory.OsgiPluginUninstalledHelper.install(OsgiPluginUninstalledHelper.java:46\)
at com.atlassian.plugin.osgi.factory.OsgiPlugin.installInternal(OsgiPlugin.java:373\)
at com.atlassian.plugin.impl.AbstractPlugin.install(AbstractPlugin.java:378\)
at com.atlassian.plugin.manager.DefaultPluginManager.lambda$addPlugins$22(DefaultPluginManager.java:1177\)
at com.atlassian.plugin.manager.PluginTransactionContext.wrap(PluginTransactionContext.java:63\)
at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:1114\)
at com.atlassian.bamboo.plugin.BambooPluginManager.addPlugins(BambooPluginManager.java:103\)
at com.atlassian.plugin.manager.DefaultPluginManager.lambda$earlyStartup$5(DefaultPluginManager.java:593\)
at com.atlassian.plugin.manager.PluginTransactionContext.wrap(PluginTransactionContext.java:63\)
at com.atlassian.plugin.manager.DefaultPluginManager.earlyStartup(DefaultPluginManager.java:528\)
at com.atlassian.plugin.manager.DefaultPluginManager.lambda$init$3(DefaultPluginManager.java:520\)
at com.atlassian.plugin.manager.PluginTransactionContext.wrap(PluginTransactionContext.java:63\)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:519\)
at com.atlassian.bamboo.container.BambooContainer.init(BambooContainer.java:227\)
at com.atlassian.bamboo.container.BambooContainer.initialise(BambooContainer.java:214\)
at com.atlassian.bamboo.upgrade.UpgradeLauncher.initialiseBambooContainer(UpgradeLauncher.java:181\)環境
8.2.4
診断
This is typically due to misconfiguration of a custom plugin. To allow Jira to start up and identify the problem plugin,
- Stop Bamboo
- Rename the BAMBOO-HOME/plugins/installed-plugins folder to anything else
- Start Bamboo
- Add plugins back one-by-one, until the problem is reproduced
原因
One known cause is wrong notation in the plugin's atlassian-plugin.xml file.
ソリューション
Check any custom-developed plugins for possible misconfigurations, and remove them until they have been tested and verified.
最終更新日 2024 年 8 月 22 日
Powered by Confluence and Scroll Viewport.