Crowd Doesn't Start if Using MySQL with Binary Logging

Still need help?

The Atlassian Community is here for you.

Ask the community


Crowd with a MySQL database generates an error similar to the following:

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


You may encounter this problem if your Crowd MySQL database configuration has the following:

  • Makes use of the InnoDB database storage engine (which is recommended)
  • Uses MySQL's default binary logging format

Crowd 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 issue no. 40360.


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

This is only needed (and valid) for MySQL versions 5.1.5 and later

To do this:

  1. Shutdown Crowd and your MySQL service (if necessary).
  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:

  4. Save your changes to this file and restart your MySQL service and Crowd

Last modified on Feb 27, 2015

Was this helpful?

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