General error "InnoDB is limited to row-logging" - Remote MariaDB

ℹ️ Support
1

I’ve just today set up a container running MariaDB to centralise databases into one server. Currently my production install runs fine on a local mysql server.

On moving the database across and updating the config, I’m met with an error 500 when browsing and requested to check the nextcloud log, which reports the following:

General error: 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

Google has suggested I add binlog_format=mixed to my my.cnf to resolve, but before I do anything I’m looking for input from the community:

  • is this the recommended permanent solution?

Thanks!

2

Yes, either the mixed mode or disable it. The documentation just refers to the database manual on this point:
https://docs.nextcloud.com/server/10/admin_manual/configuration_database/linux_database_configuration.html#mysql-mariadb-with-binary-logging-enabled

3

Excellent, thank you!