Update to 8.0.3 broken: impossible to write to binary log since BINLOG_FORMAT = STATEMENT #16008

Closed
ghost opened this Issue May 2, 2015 · 70 comments

Projects

None yet
@ghost
ghost commented May 2, 2015

Steps to reproduce

  1. Have a stable running OC 8.0.2
  2. Manual update to OC 8.0.3 by copying over the content of owncloud-8.0.3.tar.bz2
  3. Run ./occ upgrade or open the WebGUI

Expected behaviour

No exception should be thrown for the update process

Actual behaviour

Update is failing with the exception posted below

Server configuration

Operating system: Debian Jessie

Web server: NginX 1.6.3

Database: MariaDB 10.0.17

PHP version: 5.6.7

ownCloud version: (see ownCloud admin page) 8.0.2 trying to update to 8.0.3

Updated from an older ownCloud or fresh install: Updated from an older OC version

List of activated apps: Default apps + calendar, contacts, gallery+, news, notes, tasks

The content of config/config.php:

<?php
$CONFIG = array (
  'instanceid' => 'foo',
  'passwordsalt' => 'foo',
  'datadirectory' => '/var/www/owncloud/data',
  'dbtype' => 'mysql',
  'version' => '8.0.2.0',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'owncloud',
  'dbpassword' => 'foo',
  'installed' => true,
  'forcessl' => true,
  'loglevel' => 0,
  'maintenance' => false,
  'mail_smtpmode' => 'php',
  'mail_domain' => 'example.com',
  'overwriteprotocol' => 'https',
  'overwritewebroot' => '',
  'appcodechecker' => false,
  'trusted_domains' =>
  array (
    0 => 'example.com',
  ),
  'theme' => '',
  'secret' => 'foo',
  'mail_from_address' => 'admin',
  'enabledPreviewProviders' =>
  array (
    0 => 'OC\\Preview\\Image',
    1 => 'OC\\Preview\\MP3',
    2 => 'OC\\Preview\\TXT',
    3 => 'OC\\Preview\\MarkDown',
    4 => 'OC\\Preview\\Illustrator',
    5 => 'OC\\Preview\\Movie',
    6 => 'OC\\Preview\\MSOffice2003',
    7 => 'OC\\Preview\\MSOffice2007',
    8 => 'OC\\Preview\\MSOfficeDoc',
    9 => 'OC\\Preview\\OpenDocument',
    10 => 'OC\\Preview\\PDF',
    11 => 'OC\\Preview\\Photoshop',
    12 => 'OC\\Preview\\Postscript',
    13 => 'OC\\Preview\\StarOffice',
    14 => 'OC\\Preview\\SVG',
    15 => 'OC\\Preview\\TIFF',
    16 => 'OC\\Preview\\Movie',
    17 => 'OC\\Preview\\MSOfficeDoc',
    18 => 'OC\\Preview\\MSOffice2003',
    19 => 'OC\\Preview\\MSOffice2007',
    20 => 'OC\\Preview\\OpenDocument',
    21 => 'OC\\Preview\\StarOffice',
  ),
);

Are you using external storage, if yes which one: no

Are you using encryption: no

Are you using an external user-backend, if yes which one: No

Client configuration

Not relevant

Logs

Web server error log

Nothing logged as the exception is thrown before.

ownCloud log (data/owncloud.log)

Nothing logged as the exception is thrown before.

Browser log

Not relevant

Other logs

An unhandled exception has been thrown:
exception 'PDOException' with message '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.' in /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:91
Stack trace:
#0 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(91): PDOStatement->execute(Array)
#1 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(989): Doctrine\DBAL\Driver\PDOStatement->execute(Array)
#2 /var/www/owncloud/lib/private/db/connection.php(132): Doctrine\DBAL\Connection->executeUpdate('DELETE FROM oc_...', Array, Array)
#3 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(595): OC\DB\Connection->executeUpdate('DELETE FROM *PR...', Array, Array)
#4 /var/www/owncloud/lib/private/appconfig.php(220): Doctrine\DBAL\Connection->delete('*PREFIX*appconf...', Array)
#5 /var/www/owncloud/lib/private/allconfig.php(152): OC\AppConfig->deleteKey('core', 'cronErrors')
#6 /var/www/owncloud/lib/base.php(579): OC\AllConfig->deleteAppValue('core', 'cronErrors')
#7 /var/www/owncloud/lib/base.php(1026): OC::init()
#8 /var/www/owncloud/console.php(12): require_once('/var/www/ownclo...')
#9 /var/www/owncloud/occ(11): require_once('/var/www/ownclo...')
#10 {main}

Next exception 'Doctrine\DBAL\Driver\PDOException' with message '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.' in /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:93
Stack trace:
#0 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(989): Doctrine\DBAL\Driver\PDOStatement->execute(Array)
#1 /var/www/owncloud/lib/private/db/connection.php(132): Doctrine\DBAL\Connection->executeUpdate('DELETE FROM oc_...', Array, Array)
#2 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(595): OC\DB\Connection->executeUpdate('DELETE FROM *PR...', Array, Array)
#3 /var/www/owncloud/lib/private/appconfig.php(220): Doctrine\DBAL\Connection->delete('*PREFIX*appconf...', Array)
#4 /var/www/owncloud/lib/private/allconfig.php(152): OC\AppConfig->deleteKey('core', 'cronErrors')
#5 /var/www/owncloud/lib/base.php(579): OC\AllConfig->deleteAppValue('core', 'cronErrors')
#6 /var/www/owncloud/lib/base.php(1026): OC::init()
#7 /var/www/owncloud/console.php(12): require_once('/var/www/ownclo...')
#8 /var/www/owncloud/occ(11): require_once('/var/www/ownclo...')
#9 {main}

Next exception 'Doctrine\DBAL\Exception\DriverException' with message 'An exception occurred while executing 'DELETE FROM oc_appconfig WHERE appid = ? AND configkey = ?' with params ["core", "cronErrors"]:

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.' in /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:115
Stack trace:
#0 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php(116): Doctrine\DBAL\Driver\AbstractMySQLDriver->convertException('An exception oc...', Object(Doctrine\DBAL\Driver\PDOException))
#1 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(996): Doctrine\DBAL\DBALException::driverExceptionDuringQuery(Object(Doctrine\DBAL\Driver\PDOMySql\Driver), Object(Doctrine\DBAL\Driver\PDOException), 'DELETE FROM oc_...', Array)
#2 /var/www/owncloud/lib/private/db/connection.php(132): Doctrine\DBAL\Connection->executeUpdate('DELETE FROM oc_...', Array, Array)
#3 /var/www/owncloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(595): OC\DB\Connection->executeUpdate('DELETE FROM *PR...', Array, Array)
#4 /var/www/owncloud/lib/private/appconfig.php(220): Doctrine\DBAL\Connection->delete('*PREFIX*appconf...', Array)
#5 /var/www/owncloud/lib/private/allconfig.php(152): OC\AppConfig->deleteKey('core', 'cronErrors')
#6 /var/www/owncloud/lib/base.php(579): OC\AllConfig->deleteAppValue('core', 'cronErrors')
#7 /var/www/owncloud/lib/base.php(1026): OC::init()
#8 /var/www/owncloud/console.php(12): require_once('/var/www/ownclo...')
#9 /var/www/owncloud/occ(11): require_once('/var/www/ownclo...')
#10 {main}
@ghost
ghost commented May 2, 2015

BINLOG_FORMAT = STATEMENT is the default setting in common MySQL versions like 5.5 or 5.6:

https://dev.mysql.com/doc/refman/5.5/en/binary-log-setting.html
https://dev.mysql.com/doc/refman/5.6/en/binary-log-setting.html

so no custom MySQL config in place here.

@ghost ghost changed the title from Update to 8.0.2: impossible to write to binary log since BINLOG_FORMAT = STATEMENT to Update to 8.0.3: impossible to write to binary log since BINLOG_FORMAT = STATEMENT May 2, 2015
@maste9
maste9 commented May 2, 2015

Confirming bug after updating to 8.0.3 with same log output under

Server configuration

Operating system: Debian Wheezy

Web server: Apache 2.2.22-13+deb7u4

Database: MariaDB 10.0.12+maria-1~wheezy

PHP version: 5.4.39-0+deb7u2

ownCloud version: 8.0.2 trying to update to 8.0.3

Updated from an older ownCloud or fresh install: Updated from an older OC version

List of activated apps: Default apps + calendar, contacts, gallery, tasks

@ghost
ghost commented May 2, 2015

@maste9
It is save to just overwrite the existing OC 8.0.3 files with the older ones from the owncloud-8.0.2.tar.bz2 to get your instance up and running again.

@maste9
maste9 commented May 2, 2015

@RealRancor
Thx a lot! You saved my day and myself of cardiac arrest. bow down

@benurb
benurb commented May 2, 2015

If you're able to change the MariaDB configuration you can also set binlog_format = MIXED, though a explaination why this is needed would be appreciated.

Ubuntu 14.10
Apache 2.4.12
MariaDB 10.0.17
PHP 5.5.24

@bamberino

same here - also with mariadb 10.0.12, nginx 1.2.1, php 5.4.39 on debian wheezy (armv61, raspberry pi 1, model b+)....
is it a bug and will it be fixed or not?

@ghost
ghost commented May 2, 2015

@markus80
How should i know if this is a bug or not? I'm just the reporter...

@benurb
benurb commented May 2, 2015

It's a bit strange that only MariaDB seems to be affected, though MySQL 5.6 has the binlog_format set to STATEMENT by default, too.

@chtse53
chtse53 commented May 2, 2015

Same error here.
Ubuntu 14.04
Apache 2.4.7
MySQL 5.5.43
PHP 5.5.9

@ghost
ghost commented May 2, 2015

Ok, so it seems not only MariaDB is affected.

@ghost ghost changed the title from Update to 8.0.3: impossible to write to binary log since BINLOG_FORMAT = STATEMENT to Update to 8.0.3 broken: impossible to write to binary log since BINLOG_FORMAT = STATEMENT May 3, 2015
@MoonUnit2

Just chiming in here.
Debian Wheezy
MariaDB 10.0.17
Nginx 1.6.3
php-fpm 5.5.24

Glad I am not the only one with problems.

@benurb
benurb commented May 3, 2015

Like I wrote above I used binlog_format = MIXED and the update worked just fine. So it's not broken per se.

@ghost
ghost commented May 3, 2015

Hi,

it probably will be broken for shared hosting users out there when the updater app is starting to ship this version.

@ghoffart
ghoffart commented May 3, 2015

Same error here: running on Debian 6 LTS aka 6.0.10, mysql Ver 14.14 Distrib 5.5.38 and PHP 5.4.40-1~dotdeb+squeeze.1

@rokco
rokco commented May 3, 2015

just want to inform that me got the same error with debian and mysql. in my case the parameter BINLOG_FORMAT was set to STATEMENT. changing fixed the problem
mysql> SET GLOBAL binlog_format = 'MIXED';

@ghost
ghost commented May 3, 2015

If you're doing Replication in MySQL please read:

https://dev.mysql.com/doc/refman/5.6/en/binary-log-setting.html

before blindly changing this binlog_format to avoid having problems later.

@Kalimeiro

same issue, resolved when adding "binlog-format = MIXED" to /etc/mysql/my.cnf

@MoonUnit2

Do you think it would be ok to set the binlog-format back to STATEMENT after running the upgrade or leave it as MIXED?

@ibnuabdirrahim

same issue, resolved when adding "binlog-format = MIXED" to /etc/mysql/my.cnf
THANKS

@ghost
ghost commented May 4, 2015

The updater app is now shipping the update to 8.0.3, let the fun begin...

@Babzsak
Babzsak commented May 4, 2015

Same error here.

Ubuntu 14.04
Apache 2.4.7
MySQL 5.5.43
PHP 5.5.9

@bamberino

@RealRancor: hehe

@OwnCloud: have you already published any comment about that issue?

I won't do any manual fix, as long as there is no official opinion.

@benurb
benurb commented May 4, 2015

The problem is probably related to #15577 (e4f0892) which changes the isolation level to READ_COMMITTED which is not supported by the STATEMENT binlog_format.

If you are using InnoDB tables and the transaction isolation level is READ COMMITTED or READ UNCOMMITTED, only row-based logging can be used.
https://dev.mysql.com/doc/refman/5.6/en/binary-log-setting.html

As this fix seems necessary (you can read the ticket for the underlying problem here #15519) it might be the only solution to change the binlog_format. Like @markus80 said it would be nice to have an official opinion on this issue.

@MoonUnit2 In my opinion MIXED is the "better" setting especially when you're not using replication and the binary log is only used for recovery purposes. But every admin should decide this on their own.
http://serverfault.com/a/359889 has a good overview.

@loloakira

The binlog_format = MIXED paramater in the [mysqld] section of the /etc/mysql/my.cnf file also worked for me.

@throker
throker commented May 5, 2015

My database is on separate MariaDB server than ownCloud and I had to run the MySQL statement SET GLOBAL binlog_format = 'MIXED'; b/c modifying the my.cnf file didn't work, even after rebooting.

@Kalimeiro

I repeat a last time :

nano /etc/mysql/my.cnf # or path to MariaDB cnf
binlog-format = MIXED # NOT binlog_ BUT binlog-

service mysql restart

restart upgrade, it works. # for me at 1894654% it works.

@LukasReschke
Member

@karlitschek @DeepDiver1975 Any idea? – This seems rather serious.

@nickvergessen
Contributor

Related/duplicate to #7769 ?

@benurb
benurb commented May 5, 2015

@Kalimeiro It's nice that this works for you, but your information is wrong. It's indeed binlog_format not binlog-format. See https://dev.mysql.com/doc/refman/5.6/en/replication-options-binary-log.html#sysvar_binlog_format

binlog-format is correct.

@carlaschroder
Contributor

I'm thinking this is not as large an issue as it first appears, because binary logging in MySQL/MariaDB is not enabled by default. The default is error logging only in plain text. Binary logging logs a whole lot more events, so admins are cautioned that the server will take a performance hit when binary logging is enabled. This has more information https://mariadb.com/kb/en/mariadb/overview-of-the-binary-log/

@ghost
ghost commented May 5, 2015

because binary logging in MySQL/MariaDB is not enabled by default

Not exactly true. At least the Debian packages directly provided by https://downloads.mariadb.org/ have enabled the binary logging as a default in their shipped my.cnf.

@carlaschroder
Contributor

Thanks @RealRancor
OK peeps, see if this fix in the docs works for you: owncloud/documentation#1109
@karlitschek
@nickvergessen
@bantu

@maste9
maste9 commented May 7, 2015

@Kalimeiro worked for me, too! Thx!

@Kalimeiro

@benurb it's true if you run an sql command (SET) with mysql client or in you'r default init.start option (see you'r url... it's writed in black & white...) , in my case and for all having this issue, the correct solution is to add binlog-format var in you'r my.cnf, that's all.

@benurb
benurb commented May 7, 2015

@Kalimeiro Yep, you're right. Seems I've been a bit blind. binlog-format is indeed the correct way to do it in the config file.

@ghost
ghost commented May 7, 2015

Yes it is broken for share hoster users like me! I do not have access mySQL settings. So what I am supposed to do?
So far every update I did resulted in a broken OC system. If you know that there is an issue why do you not check it before your release the updater? I am no expert on this and have no clue on how to fix it. Do I have to make a fresh install?

@muellermartin

The automatic upgrade from 8.0.2 to 8.0.3 seems to be horribly broken:
First I had to manually apply a patch to overcome issue owncloud/updater#86 respectively owncloud/updater#108. And now I'm told I have to change the DB settings which do not just affect ownCloud. I'm highly curious what comes next.

@benurb
benurb commented May 7, 2015

@No-1 & @muellermartin if you already did the upgrade and are stuck because of this problem you can try to comment the line that was added in this commit: e4f0892

@FloR707
FloR707 commented May 7, 2015

Thanks for the hint that helped. I was able to finish the update after commenting out the line.

@DeepDiver1975
Member

try to comment the line that was added in this commit: e4f0892

Please be careful with commenting out this line in case you are using desktop sync clients with high traffic (many clients/users and many parallel operation) - it can cause damage.

@Ninos
Ninos commented May 8, 2015

Added binlog_format = MIXED in my my.cfg but that's just a temporary solution. You cannot force server administrators to change the binlog format to something else just that oc will work on that server. For share-hosting providers it's a big problem. I would release a bugfix-release (8.0.4) asap :-)

@bamberino

@Ninos: right

@benurb
benurb commented May 8, 2015

My opninion: I agree this one should be configurable for now, because the change is a bit problematic in a patch release. On long term I think this should be the default and not configurable any more, as it seems to cause reproducable damage to the data. If it will be configurable name the option "acceptPossibleDataDamage" or something like this. Just my opinion from reading the other ticket. Though I have to admit I never ran into this problem on my server ...

@Ninos tell this Atlassian or a lot of other companies 😄 A lot of applications force you to use at least mixed as binlog format. Basically this is a question of performance vs. data integrity/security and to be honest I prefer the later.

@psych0d0g

also, BINLOG=MIXED is just there for compatibility reasons, that format is ancient... dates back to the 90ties...

@robertoschwald

For people like me with MariaDB Replication setup (1 Master, 2 Slaves) this is a full stopper.

@cmonteroluque
Contributor

@rperezb can we test this?

@rperezb
Member
rperezb commented May 28, 2015

@cmonteroluque added to the list thx

@spyjo
spyjo commented Jun 11, 2015

Thanks @benurb I removed this line and was able to upgrade.

@DeepDiver1975
Member

Thanks @benurb I removed this line and was able to upgrade.

@spyjo FYI - without this line data loss and other issues are to be expected under high load scenarios. We do not add stuff just for pure fun or to trick our users - we do it for a reason 😉

@hibes
hibes commented Jun 11, 2015

EDIT: binlog-format = MIXED fixed it for me. Just wanted to report this anyway in case it's useful to anyone.

Dunno if you want multiple reports, here's another:

Steps to reproduce

  1. Have owncloud, not sure of version, 8.0.2, I think?
  2. Update to 8.0.3
  3. Observe error

Expected behaviour

Expected the installation to succeed

Actual behaviour

Installation failed

Server configuration

Operating system:
cat /etc/debian_version
8.0

Web server:
dpkg -l | grep apache2
ii apache2 2.4.10-10 amd64 Apache HTTP Server
ii apache2-bin 2.4.10-10 amd64 Apache HTTP Server (modules and other binary files)
ii apache2-data 2.4.10-10 all Apache HTTP Server (common files)
ii apache2-utils 2.4.10-10 amd64 Apache HTTP Server (utility programs for web servers)
rc apache2.2-common 2.4.10-6~bpo70+1+SID amd64 Transitional package for apache2
ii libapache2-mod-php5 5.6.7+dfsg-1 amd64 server-side, HTML-embedded scripting language (Apache 2 module)
rc libapache2-mod-proxy-html 3.0.1-1.1 amd64 Apache2 filter module for HTML links rewriting

Database:
pkg -l | grep mariadb-server
ii mariadb-server 10.0.16-1 all MariaDB database server (metapackage depending on the latest version)
ii mariadb-server-10.0 10.0.16-1 amd64 MariaDB database server binaries
ii mariadb-server-core-10.0 10.0.16-1 amd64 MariaDB database core server files

PHP version:
dpkg -l | grep php5
ii libapache2-mod-php5 5.6.7+dfsg-1 amd64 server-side, HTML-embedded scripting language (Apache 2 module)
ii php5 5.6.7+dfsg-1 all server-side, HTML-embedded scripting language (metapackage)
ii php5-cgi 5.6.7+dfsg-1 amd64 server-side, HTML-embedded scripting language (CGI binary)
ii php5-cli 5.6.7+dfsg-1 amd64 command-line interpreter for the php5 scripting language
ii php5-common 5.6.7+dfsg-1 amd64 Common files for packages built from the php5 source
ii php5-gd 5.6.7+dfsg-1 amd64 GD module for php5
ii php5-json 1.3.6-1 amd64 JSON module for php5
ii php5-mysql 5.6.7+dfsg-1 amd64 MySQL module for php5
ii php5-readline 5.6.7+dfsg-1 amd64 Readline module for php5

ownCloud version: (see ownCloud admin page)
Can't get in, I think it was from 8.0.2 to 8.0.3.

Updated from an older ownCloud or fresh install:
Updated.

List of activated apps:
Sharing ? Some kind of sharing app.

The content of config/config.php:

sudo cat /var/ibespwn.com/owncloud/config/config.php
<?php
$CONFIG = array (
  'instanceid' => 'ocoovhn1timn',
  'passwordsalt' => 'omitted',
  'secret' => 'omitted',
  'trusted_domains' =>
  array (
    0 => 'ibespwn.com',
  ),
  'datadirectory' => '/var/owncloud/data',
  'overwrite.cli.url' => 'https://ibespwn.com/owncloud',
  'dbtype' => 'mysql',
  'version' => '8.0.2.0',
  'dbname' => 'owncloud',
  'dbhost' => 'localhost',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'owncloud',
  'dbpassword' => 'omitted',
  'installed' => true,
  'mail_from_address' => 'owncloud',
  'mail_smtpmode' => 'php',
  'mail_domain' => 'ibespwn.com',
  'theme' => '',
  'maintenance' => false,
);

Are you using external storage, if yes which one: local/smb/sftp/...
omitted:/omitted/path/to/owncloud /omitted/path/to/owncloud/data nfs auto 0 0

Are you using encryption: yes/no
Encryption in what sense? https? Yes.

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No

Client configuration

Browser:
Chrome

Operating system:
Mac OS and Windows, same result

Logs

Web server error log

omitted.destination.dns:443 omitted.source.ip - - [11/Jun/2015:11:23:12 -0500] "GET /owncloud/core/ajax/update.php?requesttoken=omitted.token HTTP/1.1" 200 8368 "https://omitted.destination.dns/owncloud/index.php/apps/updater/update.php" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36"

ownCloud log (data/owncloud.log)

{"reqId":"e80aa81234e0a72b93e518cc833cf265","remoteAddr":"192.168.63.1","app":"core","message":"Simulated database structure update failed (exception 'PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:57\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php(57): PDO->exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/     Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/    private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/      owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/     private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main}\n\nNext exception 'Doctrine\\DBAL\\Driver\\PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:59\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection-            >exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig',     'oc_oc_appconfig...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator-         >checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#9 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#10 {main}\n\nNext exception 'Doctrine\\DBAL\\Exception\\DriverException' with message 'An exception occurred while executing 'INSERT INTO `oc_oc_appconfig_ccaz2da11dueo` SELECT * FROM             `oc_appconfig`':\n\nSQLSTATE[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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/AbstractMySQLDriver.php:115\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/      DBALException.php(116): Doctrine\\DBAL\\Driver\\AbstractMySQLDriver->convertException('An exception oc...', Object(Doctrine\\DBAL\\Driver\\PDOException))\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1027):                     Doctrine\\DBAL\\DBALException::driverExceptionDuringQuery(Object(Doctrine\\DBAL\\Driver\\PDOMySql\\Driver), Object(Doctrine\\DBAL\\Driver\\PDOException), 'INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection-   >exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator-                     >checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239):    OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater. php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main})","level":4,"time":   "2015-06-11T03:40:58+00:00"}
{"reqId":"22393d896fc289229284d51c434bce5f","remoteAddr":"omitted.source.ip","app":"core","message":"Simulated database structure update failed (exception 'PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:57\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php(57): PDO->exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/     Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/    private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/      owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/     private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main}\n\nNext exception 'Doctrine\\DBAL\\Driver\\PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:59\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection-            >exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig',     'oc_oc_appconfig...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator-         >checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#9 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#10 {main}\n\nNext exception 'Doctrine\\DBAL\\Exception\\DriverException' with message 'An exception occurred while executing 'INSERT INTO `oc_oc_appconfig_sztcjvxbh0p56` SELECT * FROM             `oc_appconfig`':\n\nSQLSTATE[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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/AbstractMySQLDriver.php:115\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/      DBALException.php(116): Doctrine\\DBAL\\Driver\\AbstractMySQLDriver->convertException('An exception oc...', Object(Doctrine\\DBAL\\Driver\\PDOException))\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1027):                     Doctrine\\DBAL\\DBALException::driverExceptionDuringQuery(Object(Doctrine\\DBAL\\Driver\\PDOMySql\\Driver), Object(Doctrine\\DBAL\\Driver\\PDOException), 'INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection-   >exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator-                     >checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239):    OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater. php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main})","level":4,"time":   "2015-06-11T16:04:36+00:00"}
{"reqId":"0b3d8fe2cc14a45097b77c992102ee4f","remoteAddr":"omitted.source.ip","app":"core","message":"Simulated database structure update failed (exception 'PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:57\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php(57): PDO->exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/     Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/    private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/      owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/     private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main}\n\nNext exception 'Doctrine\\DBAL\\Driver\\PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:59\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection-            >exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig',     'oc_oc_appconfig...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator-         >checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#9 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#10 {main}\n\nNext exception 'Doctrine\\DBAL\\Exception\\DriverException' with message 'An exception occurred while executing 'INSERT INTO `oc_oc_appconfig_143ek9xbomdi4` SELECT * FROM             `oc_appconfig`':\n\nSQLSTATE[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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/AbstractMySQLDriver.php:115\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/      DBALException.php(116): Doctrine\\DBAL\\Driver\\AbstractMySQLDriver->convertException('An exception oc...', Object(Doctrine\\DBAL\\Driver\\PDOException))\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1027):                     Doctrine\\DBAL\\DBALException::driverExceptionDuringQuery(Object(Doctrine\\DBAL\\Driver\\PDOMySql\\Driver), Object(Doctrine\\DBAL\\Driver\\PDOException), 'INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection-   >exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator-                     >checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239):    OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater. php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main})","level":4,"time":   "2015-06-11T16:18:53+00:00"}
{"reqId":"d55e08d35a26bbe9dcd90dd9c7b2a5fb","remoteAddr":"omitted.source.ip","app":"core","message":"Simulated database structure update failed (exception 'PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:57\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php(57): PDO->exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/     Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/    private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/      owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/     private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main}\n\nNext exception 'Doctrine\\DBAL\\Driver\\PDOException' with message '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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/PDOConnection.php:59\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1025): Doctrine\\DBAL\\Driver\\PDOConnection-            >exec('INSERT INTO `oc...')\n#1 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection->exec('INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig',     'oc_oc_appconfig...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator->checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator-         >checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239): OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(226): OC\\Updater->checkCoreUpgrade()\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#9 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#10 {main}\n\nNext exception 'Doctrine\\DBAL\\Exception\\DriverException' with message 'An exception occurred while executing 'INSERT INTO `oc_oc_appconfig_9glj9jtwiql91` SELECT * FROM             `oc_appconfig`':\n\nSQLSTATE[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.' in \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Driver\/AbstractMySQLDriver.php:115\nStack trace:\n#0 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/      DBALException.php(116): Doctrine\\DBAL\\Driver\\AbstractMySQLDriver->convertException('An exception oc...', Object(Doctrine\\DBAL\\Driver\\PDOException))\n#1 \/var\/omitted.dns.com\/owncloud\/3rdparty\/doctrine\/dbal\/lib\/Doctrine\/DBAL\/Connection.php(1027):                     Doctrine\\DBAL\\DBALException::driverExceptionDuringQuery(Object(Doctrine\\DBAL\\Driver\\PDOMySql\\Driver), Object(Doctrine\\DBAL\\Driver\\PDOException), 'INSERT INTO `oc...')\n#2 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(214): Doctrine\\DBAL\\Connection-   >exec('INSERT INTO `oc...')\n#3 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(116): OC\\DB\\Migrator->copyTable('oc_appconfig', 'oc_oc_appconfig...')\n#4 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/migrator.php(91): OC\\DB\\Migrator-                     >checkTableMigrate(Object(Doctrine\\DBAL\\Schema\\Table))\n#5 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db\/mdb2schemamanager.php(113): OC\\DB\\Migrator->checkMigrate(Object(Doctrine\\DBAL\\Schema\\Schema))\n#6 \/var\/omitted.dns.com\/owncloud\/lib\/private\/db.php(239):    OC\\DB\\MDB2SchemaManager->simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#7 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(254): OC_DB::simulateUpdateDbFromStructure('\/var\/omitted.dns.co...')\n#8 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater. php(226): OC\\Updater->checkCoreUpgrade()\n#9 \/var\/omitted.dns.com\/owncloud\/lib\/private\/updater.php(150): OC\\Updater->doUpgrade('8.0.3.4', '8.0.2.0')\n#10 \/var\/omitted.dns.com\/owncloud\/core\/ajax\/update.php(58): OC\\Updater->upgrade()\n#11 {main})","level":4,"time":   "2015-06-11T16:23:12+00:00"}

Browser log

An exception occurred while executing 'INSERT INTO `oc_oc_appconfig_9glj9jtwiql91` SELECT * FROM `oc_appconfig`': 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.

screen shot 2015-06-11 at 11 19 26 am

@cmonteroluque
Contributor

close. Configure DB as documented

@ghoffart

Eh, if this is closed, then should there be another ticket that asks for a clear help for admins during upgrade? The current message is not that helpful.

@Ninos
Ninos commented Jun 17, 2015

@cmonteroluque and that's really your solution? It's like saying: "Just use firefox as browser, than you don't have such problems". Sometimes a customer cannot change the binary log on his system. I know at least two persons which cannot upgrade to newest owncloud version because of that problem, just because their hoster is not supporting such binary log setting..

@DeepDiver1975
Member

We cannot come up in the release cycle of oc8 with a different approach to ensure you will not loose your data.
For the development cycle we will invest some more brain power to address this issue for a much broader installation base.

You are free to remove that single line as described above to remove the explicit setting of that isolation level.

@Ninos
Ninos commented Jun 17, 2015

@spyjo FYI - without this line data loss and other issues are to be expected under high load scenarios. We do not add stuff just for pure fun or to trick our users - we do it for a reason 😉

So removing that line is not really a solution :D I then really hope, you'll fix that in the new oc-majorrelease. There're enough customers which need a fix for that :)

@dhuyvetter

As I am shared hosting I cannot just change my MySQL settings. I have filed a support question with my hoster and just have to hope that they will want to make the changes just for me.

@fg-ok
fg-ok commented Jun 19, 2015

@DeepDiver1975 FYI: Stumbled just over the same issue on a fresh new install! So it's not just an issue for the concerned users that try to keep their systems up2date. Fresh users are directly welcomed by this issue and have to figure out why they cannot use owncloud! Maybe you should keep that in mind!?

So removing that line is not really a solution :D I then really hope, you'll fix that in the new oc-
majorrelease. There're enough customers which need a fix for that :)

This! Especially when you try to set up a fresh system! That's a typical situation where you don't want to "hack" around!

@RobinJ1995

So I have to change my database configuration which has negative effects on other functionality, just to be able to do a "minor" version upgrade of ownCloud? I think I'll just downgrade to and pin 8.0.2 until the developers have figured it out 👍 Frankly, this is not acceptable.

@DeepDiver1975
Member

@fg-ok @RobinJ1995 taken into account that comments on the Internet tend to be interpreted more aggressive then intended - I ignore any negative tendencies of your comments and welcome you to come up with an alternative solution.

Contributions are very much welcome!

this-is-open-source

@Ninos
Ninos commented Jul 8, 2015

Is it fixed now or just closed because of "won't fix"?
PS: Because I cannot see some relevant changes about that in changelog I would increase the milestone to 8.1.1..

@DeepDiver1975
Member

Is it fixed now or just closed because of "won't fix"?

closed because the necessary settings are documented - nothing to do at the moment

@Ninos
Ninos commented Jul 8, 2015

Can you please tell the community why you don't won't to fix such "sev2-high" tagged bug? Because it's not possible to fix (reasons please) or just because your server is not affected by that bug? A statement for that's still missing. (May also on installation requirements, that's not working on all shared-hosted systems e.g. with bin_log = statement).

I'm also working on lots of open-source projects, e.g. an isp for shared hosters (i-mscp). OwnCloud is not running on such clean installed servers with default configurations.

Again, the communication with the community is very weak here. If your team don't want to fix that bug, at least we want to hear the reasons for (e.g. in an official statement [as blog entry]). It also supports the work of shared-hosting providers because then we're able to refer to your statement.

Kindest regards,
Ninos

@saamo
saamo commented Sep 17, 2015

It was already said somewhere above but make sure to place the option under the [mysqld] header in /etc/mysql/my.cnf unless it won't work.

[mysqld]
binlog_format = MIXED
@boldandbusted

Just another reporter for this issue on a brand new installation with OwnCloud 8.1.3. :( What is this offending SQL doing that Owncloud needs to merit such out-the-gate unhandled errors (which asks the users to report...). Thanks. UPDATE: If there's a more relevant bug, please linkslap me. :)

@ghost
ghost commented Oct 8, 2015

@boldandbusted Just set the correct binlog_format needed by oC

@ghost
ghost commented Oct 30, 2015

Just stumbled again over the comment of @Ninos in #16008 (comment). Just to clarify, this is not a bug but a requirement. The reason why was stated here: #16008 (comment)

@rikur
rikur commented May 3, 2016

lol such great ux

@wedojava
wedojava commented May 24, 2016 edited

HI! @saamo
My Lucky. What can I do my best for thank you very much!!!!!!!!!

I got it! 2 days last! because i don't know "place the option under the [mysqld] header in /etc/mysql/my.cnf",I had saw the documents from MySQL and MairaDB and OC yet,but also don't know that, thanks you!!!

@saamo
saamo commented May 24, 2016

@wedojava, glad it helped you :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment