Upgrading from Xibo 1.7.4 to 1.7.7

alex · May 13, 2016, 9:16am

In 1.7.7 we change the transaction isolation level to READ COMMITTED to support running on systems where there is MySQL replication going on. Unfortunately that’s incompatible with setting up MySQL to BINLOG_FORMAT = STATEMENT.

You can change that setting to MIXED in your MySQL configuration and restart MySQL to get things working if it’s appropriate in your environment. If you’re not using a replicated MySQL instance then as far as I’m aware there’s no implication for making that change.

I’ve logged it as a bug to be investigated here:

github.com/xibosignage/xibo

1.7.7 unable to log in if MySQL binlog format is STATEMENT

opened 09:33AM - 13 May 16 UTC

closed 09:05AM - 03 Jun 16 UTC

alexharrington

bug

If MySQL BINLOG_FORMAT is set to STATEMENT (vs MIXED or ROW) then the Symphony s…ession handler fails with the following error: > Error writing session: SQLSTATE[HY000]: 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 Setting MySQL to used MIXED format will resolve this as a work around - if it's appropriate to do so in your environment. Investigate if we can work around this in code, or failing that add an install/upgrade time check to ensure that the BINLOG format is suitable. Originally reported here: https://community.xibo.org.uk/t/upgrading-from-xibo-1-7-4-to-1-7-7/5972/8