Confluence will not start due to incorrect log format

This Knowledge Base article was written specifically for the Atlassian Server platform. Due to the Restricted functions in Atlassian Cloud apps, the contents of this article cannot be applied to Atlassian Cloud applications.

Problem

Confluence will not start and the following appears in the atlassian-confluence.log:

caused by: org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: Could not save object; uncategorized SQLException for SQL []; SQL state [HY000]; error code [1665]; Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.; nested exception is java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.

Cause

If you are using InnoDB tables and the transaction isolation level is READ COMMITTED or READ UNCOMMITTED, only row-based logging can be used. The error is caused by the binlog_format setting in my.cnf being set to "statement" . For more information see https://dev.mysql.com/doc/refman/5.7/en/binary-log-setting.html.

Resolution

 

Change the  binlog_format setting in my.cnf (mysqld) to

binlog_format=row


The my.cnf file is typically in /etc/my.cnf.

 

 

Last modified on Jul 17, 2017

Was this helpful?

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