Restoring a Bamboo instance after a crash
Symptoms
Bamboo cannot start up. The Bamboo log shows errors like:
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.atlassian.bamboo.configuration.AdministrationConfiguration com.atlassian.bamboo.persister.file.FileBasedPersister.getAdministrationConfiguration()] threw exception; nested exception is com.thoughtworks.xstream.io.StreamException: : input contained no data
...
Caused by: com.thoughtworks.xstream.io.StreamException: : input contained no data
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:80)
....
Caused by: java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2982)
Cause
Bamboo has been shut down improperly. Possible causes are:
- Ran out of disk space on the Bamboo server
- Power outage on the Bamboo server
Resolution
Check all files in <BAMBOO_HOME>/xml-data/configuration/*.xml
and see if they are ok.
If not please restore these files from a Bamboo backup zip. You can simply unzip the backup and copy the administration.xml
file from the <backup-zip>/configuration
directory.
If you don't have a backup you can:
- change
bamboo.home
in<bamboo-install>/atlassian-bamboo/WEB-INF/classes/bamboo-init.properties
to a temporary location<temp-bamboo-home>
. - if you are using an external database - create a new temporary database for this procedure.
- start Bamboo, run through the setup wizard entering the data as if in your production instance (except for db name). File
<temp-bamboo-home>/xml-data/configuration/administration.xml
will be created. - copy the above file into
<bamboo-home>/xml-data/configuration/
. - Double check the copied files for correctness regarding paths and URLs.
This should restore the missing files for your production instance.
Last modified on Mar 13, 2017
Powered by Confluence and Scroll Viewport.