Bamboo does not start due to empty administration.xml file
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
Problem
When attempting to start Bamboo, the service does not start, and the following appears in the atlassian-bamboo.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2017-01-03 16:57:47,056 ERROR [localhost-startStop-1] [ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'remoteEventsJmsTemplate' defined in class path resource [applicationContextManagers.xml]: Cannot resolve reference to bean 'jmsMessageConverter' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmsMessageConverter' defined in class path resource [applicationContextCommon.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.bamboo.v2.build.queue.BambooMessageConverter]: Constructor threw exception; nested exception is com.thoughtworks.xstream.io.StreamException:
...
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmsMessageConverter' defined in class path resource [applicationContextCommon.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.bamboo.v2.build.queue.BambooMessageConverter]: Constructor threw exception; nested exception is com.thoughtworks.xstream.io.StreamException:
...
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.bamboo.v2.build.queue.BambooMessageConverter]: Constructor threw exception; nested exception is com.thoughtworks.xstream.io.StreamException:
...
Caused by: com.thoughtworks.xstream.io.StreamException:
...
at com.atlassian.bamboo.persister.file.FileBasedPersister.getAdministrationConfiguration(FileBasedPersister.java:280)
at com.atlassian.bamboo.configuration.AdministrationConfigurationAccessorImpl.getAdministrationConfiguration(AdministrationConfigurationAccessorImpl.java:26)
...
Caused by: java.io.EOFException: input contained no data
...Cause
This issue is caused by the <bamboo-home>/xml-data/configuration/administration.xml file being empty.
This file is confirmed by these two lines in the stack, included above:
1
2
at com.atlassian.bamboo.persister.file.FileBasedPersister.getAdministrationConfiguration(FileBasedPersister.java:280)
at com.atlassian.bamboo.configuration.AdministrationConfigurationAccessorImpl.getAdministrationConfiguration(AdministrationConfigurationAccessorImpl.java:26)Resolution
If you have a backup of
administration.xml, please restore it to theconfigurationdirectory.The administration.xml file is located in the following paths:
Bamboo 7 and earlier:
<bamboo-home>/xml-data/configuration/administration.xml
Bamboo 8 and later:
<bamboo-shared-home>/configuration/administration.xml
If you do not have recent backup, but have recently generated Support Zip you can find this file under <archive>/application-config/administration.xml.
Otherwise, you will need to create one. This can be done by installing a separate instance of Bamboo, configured the same as your main Server, and then moving the file to the
configurationdirectory on your original Bamboo instance.
Was this helpful?