Getting an ImportExportException error when trying to backup a confluence

Question

When trying to backup a DB manually, on confluence server 6.15.9

Getting the following error:

-- url: /admin/dobackup.action | traceId: 91461f5570ee77a8 | userName: adminexample | referer: https://confluence.example.com/admin/backup.action | action: dobackup
org.springframework.orm.hibernate.HibernateSystemException: Transaction was marked for rollback only; cannot commit; nested exception is net.sf.hibernate.TransactionException: Transaction was marked for rollback only; cannot commit
at org.springframework.orm.hibernate.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:597)
at org.springframework.orm.hibernate.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:353)
at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:375)
at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:337)
at com.atlassian.confluence.core.persistence.hibernate.HibernateAnyTypeDao.findAllPersistentObjectsHandlesUntyped(HibernateAnyTypeDao.java:122)
at com.atlassian.confluence.core.persistence.hibernate.HibernateAnyTypeDao.findAllPersistentObjectsHibernateHandles(HibernateAnyTypeDao.java:117)
at com.atlassian.confluence.importexport.impl.BackupExporter.getHandlesOfObjectsForExport(BackupExporter.java:26)
at com.atlassian.confluence.importexport.impl.AbstractXmlExporter.backupEntities(AbstractXmlExporter.java:199)
at com.atlassian.confluence.importexport.impl.AbstractXmlExporter.backupEverything(AbstractXmlExporter.java:99)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.backupEverything(FileXmlExporter.java:95)
at com.atlassian.confluence.importexport.impl.AbstractXmlExporter.doExport(AbstractXmlExporter.java:93)
at com.atlassian.confluence.importexport.impl.FileXmlExporter.doExportInternal(FileXmlExporter.java:60)...
...
Caused by: net.sf.hibernate.TransactionException: Transaction was marked for rollback only; cannot commit
at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:217)
at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:68)
at com.atlassian.hibernate.util.TransactionHelper$RestartOnCommitTransaction.commit(TransactionHelper.java:45)
at com.atlassian.hibernate.adapter.adapters.TransactionV2Adapter.commit(TransactionV2Adapter.java:30)
at com.atlassian.confluence.core.persistence.hibernate.HibernateAnyTypeDao$AllPersistentObjectsHandlesLoader.doInHibernate(HibernateAnyTypeDao.java:326)
at com.atlassian.confluence.core.persistence.hibernate.HibernateAnyTypeDao.lambda$findAllPersistentObjectsHandlesUntyped$3(HibernateAnyTypeDao.java:123)
at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:370)

https://confluence.example.com/admin/backup.action

Go to Confluence administration > Backup and Export > and click export

any of the options doesn't effect the error and the backup fails

Stephen Sifers · Answer

Hello Anatoly,

Thanks for the follow-up and further information about your database. The issue you’re reporting can be due to database corruption, which is why I asked for you to attempt a local database backup. I would ask for you to review the following doc on exporting to XML to further troubleshoot the matter: Troubleshooting failed XML site backups.

If you’re still having issues after following the above article, please let us know.

Regards,
Stephen Sifers

Anatoly Fishgang_1d2ab0 · Answer

Hello Stephen,

I am running a docker container with:

PostgreSQL 9.6.15 on x86_64-pc-linux (Alpine 8.3.0)

the DB is being exported via pg_dump command without any errors.

Stephen Sifers · Answer

Hello Anatoly,

Thanks for reaching out about your issues with backing up Confluence from within Confluence. From the error you provided and the logs (which are super helpful) it looks like an issue with the database. From this, we believe the issue lies within your database configuration/setup which might be causing this issue. We would ask you to attempt a database backup from your database application itself to ensure no errors are present there.

If your database backup succeeded without error, please let us know which database application you’re using so we may investigate further.

Regards,
Stephen SIfers