Your shared Bamboo configuration version is too old comparing to local node Bamboo version

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.


When upgrading Bamboo to version 8.0 or higher, the application will not start.


Upgrading Bamboo to version 8.0+.


The following error message can be seen in the logs (atlassian-bamboo.log) right after Bamboo is started.

2021-09-17 15:41:25,515 INFO [localhost-startStop-1] [lifecycle] *   Bamboo is starting up     *
2021-09-17 15:41:25,515 INFO [localhost-startStop-1] [lifecycle] *******************************
2021-09-17 15:41:26,858 ERROR [localhost-startStop-1] [DefaultAtlassianBootstrapManager] Home is not configured properly: 
com.atlassian.config.ConfigurationException: Your shared Bamboo configuration (/bamboo-home/xml-data/configuration) version (60805) is too old comparing to local node Bamboo version (70212). Shared home Bamboo version expected to be equal or greater than local Bamboo node version.
	at com.atlassian.bamboo.setup.DefaultBootstrapManager.afterConfigurationLoaded(
	at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(
	at com.atlassian.bamboo.setup.BootstrapLoaderListener.contextInitialized(
	at org.apache.catalina.core.StandardContext.listenerStart(
	at org.apache.catalina.core.StandardContext.startInternal(
	at org.apache.catalina.util.LifecycleBase.start(
	at org.apache.catalina.core.ContainerBase$
	at org.apache.catalina.core.ContainerBase$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
2021-09-17 15:41:26,860 INFO [localhost-startStop-1] [lifecycle] Bamboo home directory: /bamboo-home
2021-09-17 15:41:26,860 INFO [localhost-startStop-1] [lifecycle] Default charset: UTF-8, file name ecoding: UTF-8
2021-09-17 15:41:26,869 INFO [localhost-startStop-1] [UpgradeLauncher] Upgrades not performed since the application has not been set up yet.

In the UI, you'll see a long error related to FreeMarker templates, which is thrown because Bamboo couldn't startup properly due to the error above.

io.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
	at io.atlassian.util.concurrent.LazyReference.getInterruptibly(
	at io.atlassian.util.concurrent.LazyReference.get(
	at com.atlassian.bamboo.ww2.BambooFreemarkerManagerSoyHelpers$SoyHelper.renderNoCache(
	at com.atlassian.bamboo.ww2.BambooFreemarkerManagerSoyHelpers$SoyHelper.render(
	at com.atlassian.bamboo.ww2.BambooFreemarkerManagerSoyHelpers$SoyHelper.render(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at freemarker.ext.beans.BeansWrapper.invokeMethod(
	at freemarker.ext.beans.ReflectionCallableMemberDescriptor.invokeMethod(
	at freemarker.ext.beans.MemberAndArguments.invokeMethod(
	at freemarker.ext.beans.OverloadedMethodsModel.exec(
	at freemarker.core.MethodCall._eval(
	at freemarker.core.Expression.eval(


Caused by: java.lang.NullPointerException
	at com.atlassian.bamboo.ww2.BambooFreemarkerManager$1.get(
	at com.atlassian.bamboo.ww2.BambooFreemarkerManager$1.get(
	at io.atlassian.util.concurrent.Lazy$Strong.create(
	at io.atlassian.util.concurrent.LazyReference$
	at io.atlassian.util.concurrent.LazyReference.getInterruptibly(
	... 112 more


Starting Bamboo 8, a new file was introduced to the home folder, called bamboo-shared.cfg.xml. It contains the application's build number:

bamboo-shared.cfg.xml example
<?xml version="1.0" encoding="UTF-8"?><application-configuration>
    <property name="build-number">80009</property>

One of the upgrade tasks checks if the new local home is using an older share home. If, by any reason, that file gets corrupted and shows an older build number than your current one, the upgrade will fail.

E.g., if your current version is 7.2.5 (build 70212), but the file refers to the build number as 60805 (Bamboo 6.8.1), once you try to upgrade to Bamboo 8.0+, it will not match the above criteria and the upgrade will fail.


Simply update the file and replace the build number with the new one (which you can get from the error in the logs).

  1. Stop Bamboo.
  2. Make a backup and then edit the <bamboo-home>/xml-data/configuration/bamboo-shared.cfg.xml file, changing the build number to the one pointed by the error message, at the following property:

        <property name="build-number">80009</property> 
  3. The file should then look like this:

    <?xml version="1.0" encoding="UTF-8"?><application-configuration>
        <property name="build-number">80009</property>
  4. Delete everything inside the following folders (but not the folders themselves):

  5. Start Bamboo.

That's it!

Last modified on Sep 20, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.