Bamboo fails to start due to java.io.FileNotFoundException
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
Symptom
Bamboo fails to start and the following message is found in <BambooInstallationDirectory>/logs/catalina.out (Linux) or <BambooInstallationDirectory>\logs\catalina.out (Windows):
1
2
3
4
5
6
7
8
9
10
11
12
13
java.io.FileNotFoundException: <BambooHome>/logs/atlassian-bamboo.log (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
[...]
2015-07-08 22:07:40,835 INFO [localhost-startStop-1] [BootstrapLoaderListener] Starting BootstrapLoaderListener
2015-07-08 22:07:40,835 INFO [localhost-startStop-1] [lifecycle] *******************************
2015-07-08 22:07:40,835 INFO [localhost-startStop-1] [lifecycle] * Bamboo is starting up *
2015-07-08 22:07:40,835 INFO [localhost-startStop-1] [lifecycle] *******************************
2015-07-08 22:07:40,836 INFO [localhost-startStop-1] [ServletContextHolder] Setting servlet context: Bamboo
[...]
2015-07-08 22:07:43,791 ERROR [localhost-startStop-1] [AbstractUpgradeManager] java.io.FileNotFoundException: <BambooHome>/xml-data/configuration/administration.xml (Permission denied)
java.io.FileNotFoundException: <BambooHome>/xml-data/configuration/administration.xml (Permission denied)
at java.io.FileOutputStream.open(Native Method)Note: The specific file name or directory may be different.
Cause
The Bamboo process does not have permission to read or write parts of the contents of the <BambooHome> directory (where <BambooHome> is the Bamboo home directory).
Resolution
To resolve this problem, grant the user that is running Bamboo full control to the <BambooHome> directory:
Linux:
1
chown <USER>.<GROUP> -R <BambooHome>where <USER> is the username of the user that the Bamboo process runs as and <GROUP> is the primary group that this user is a member of.
Windows:
Grant full control permissions to the <BambooHome> directory on the directory settings.
Was this helpful?