Confluence crashes due to insufficient disk space and truncated confluence.cfg.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
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:
1
2
3
4
5
6
7
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.
...
Cause
The system ran out of disk space.
Resolution
Setup a new instance and ensure the setup is successful
Copy the
confluence.cfg.xmlover to the old instance and make sure the license used is validMake the necessary changes such as the connection url to match the configuration in the older instance
Was this helpful?