Confluence crashes due to insufficient disk space and truncated confluence.cfg.xml file

Still need help?

The Atlassian Community is here for you.

Ask the community


Confluence or the server on which it resides crashes. As a result, the confluence.cfg.xml file gets truncated to a zero kb file. In contrast, the other folders within <confluence-home> remain intact. The following appears in the atlassian-confluence.log:

2008-01-07 10:07:05,918 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 2.6.0 (build #913)
2008-01-07 10:07:07,560 ERROR [main] [atlassian.config.bootstrap.DefaultAtlassianBootstrapManager] init Home is not configured properly: com.atlassian.config.ConfigurationException: Failed to parse config file: Error on line -1 of document  : Premature end of file. Nested exception: Premature end of file.
2008-01-07 10:07:07,601 FATAL [main] [atlassian.confluence.setup.ConfluenceConfigurationListener] contextInitialized An error was encountered while bootstrapping Confluence (see below): 
2008-01-07 10:07:09,315 FATAL [http-7000-Processor4] [confluence.setup.johnson.WebAppContextPathCheck] check Bootstrap did not initialize.
2008-01-07 10:07:09,340 FATAL [http-7000-Processor4] [confluence.setup.johnson.WebAppContextPathCheck] check Bootstrap did not initialize.


The system ran out of disk space.


  1. Setup a new instance and ensure the setup is successful
  2. Copy the confluence.cfg.xml over to the old instance and make sure the license used is valid
  3. Make the necessary changes such as the connection url to match the configuration in the older instance



Last modified on Mar 30, 2016

Was this helpful?

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