Confluence will not start due to incorrect log format

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

本ナレッジベースはアトラシアンの サーバー プラットフォーム向けに記載されたものです。Atlassian Cloud との機能の違いにより、本記事の内容を Atlassian Cloud アプリケーションに適用することはできません。

問題

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.

原因

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.

ソリューション

 

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

binlog_format=row


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

 

 

最終更新日 2017 年 7 月 17 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.