Unable to Start Confluence Due to I/O errors during LOB access

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.

Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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

Symptoms

Starting Confluence fails. The following appears in the atlassian-confluence.log:

2011-04-08 13:38:29,332 ERROR [main] [atlassian.confluence.event.ConfluenceEventManager] publishEvent An exception was encountered while processing the event: com.atlassian.confluence.event.events.admin.ConfluenceReadyEvent[source=com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager@1f34137c]
org.springframework.orm.hibernate.HibernateSystemException: I/O errors during LOB access; nested exception is net.sf.hibernate.HibernateException: I/O errors during LOB access
Caused by: net.sf.hibernate.HibernateException: I/O errors during LOB access

Cause

The persistance library is trying to spool a database CLOB object and failing because it can't write to disk.

Resolutions

Check that:

  1. Check to see if the temporary directory (set using java.io.tmpdir or System_Temp) has enough disk space.
  2. Ensure that the user running Confluence can write the temporary directory.
  3. Try setting -Djava.io.tmpdir=<a_known_path> in your Confluence system property
  4. If you are running Confluence as a Windows Service and see this line in the stacktrace:
Caused by: java.io.IOException: The system cannot find the path specified
  • Check your settings within the JAVA_OPTS variable. Each entry needs to be on a new line. Also check to make sure there aren't any trailing spaces following -Djava.io.tmpdir=<path>. If there are, it will be interpreted as part of the directory path.
Last modified on Dec 18, 2024

Was this helpful?

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