Confluence will not start using MySQL 5.1.5+ with STATEMENT binary logging

お困りですか?

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

コミュニティに質問

問題

Confluence installation will not start properly when it's using MySQL 5.1.5+ with InnoDB and the default binary logging format - i.e. 'STATEMENT'

診断

atlassian-confluence.log に次のエラーが返されます。

Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

または

2012-07-26 04:28:24,589 ERROR [http-80-1] [sf.hibernate.util.JDBCExceptionReporter] logExceptions 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.

原因

Confluence uses the 'READ-COMMITTED' transaction isolation level with MySQL, which currently only supports row-based binary logging. For more information about this, please refer to MySQL Bug #40360.

ソリューション

To fix this problem, you must configure MySQL's binary logging format to use 'row-based' binary logging:

  1. Shutdown Confluence and your MySQL database
  2. Open the MySQL configuration file (my.cnf) in a text editor
    (info) On UNIX-based systems, this file may be located in the /etc directory
  3. Locate the binlog_format property in this file in the [mysqld] section and ensure that its value is row, such that you end up with:

    binlog_format=row
  4. Save your changes to this file
  5. Restart Confluence and your MySQL database
Last modified on Mar 30, 2016

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

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