Bamboo startup fails with error "Bamboo bootstrap failed: Couldn't save bamboo-shared.cfg.xml"

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.

*Except Fisheye and Crucible

Summary

After a Bamboo upgrade, when starting Bamboo, the bootstrap fails with the below error on UI:

1 Bamboo bootstrap failed: Couldn't save bamboo-shared.cfg.xml to <BAMBOO_HOME>/shared/configuration directory.

Environment

Bamboo version 8+ running on Windows

Diagnosis

The Bamboo User interface shows an error like the one below.

(Auto-migrated image: description temporarily unavailable)

An error printed in the <BAMBOO_INSTALL_DIR>/logs/bamboo-stderror file regarding permission

1 2 3 4 5 6 7 java.io.FileNotFoundException: D:\Bamboo\bamboo-home\logs\atlassian-bamboo-access.log (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:133) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)

Cause

The user or the service account that is running the Bamboo doesn't have full read/write permission on the <BAMBOO-HOME> directory.

Solution

Please assign the user or the service-account that starts Bamboo has complete permission on the <BAMBOO_HOME> directory. Then, restart Bamboo and start the Bamboo setup process again. This should fix the issue if all the permissions are correctly set.

Updated on February 28, 2025

Still need help?

The Atlassian Community is here for you.