New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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 · 78 comments

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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 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

This comment has been minimized.

Show comment
Hide comment
@maste9

maste9 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

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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.

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

This comment has been minimized.

Show comment
Hide comment
@maste9

maste9 May 2, 2015

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

maste9 commented May 2, 2015

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

@benurb

This comment has been minimized.

Show comment
Hide comment
@benurb

benurb 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

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

This comment has been minimized.

Show comment
Hide comment
@bamberino

bamberino May 2, 2015

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?

bamberino commented May 2, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 2, 2015

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

ghost commented May 2, 2015

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

@benurb

This comment has been minimized.

Show comment
Hide comment
@benurb

benurb 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.

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

This comment has been minimized.

Show comment
Hide comment
@chtse53

chtse53 May 2, 2015

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

chtse53 commented May 2, 2015

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

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 2, 2015

Ok, so it seems not only MariaDB is affected.

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

This comment has been minimized.

Show comment
Hide comment
@MoonUnit2

MoonUnit2 May 3, 2015

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.

MoonUnit2 commented May 3, 2015

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

This comment has been minimized.

Show comment
Hide comment
@benurb

benurb 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.

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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.

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

This comment has been minimized.

Show comment
Hide comment
@ghoffart

ghoffart 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

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

This comment has been minimized.

Show comment
Hide comment
@rokco

rokco 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';

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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.

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

This comment has been minimized.

Show comment
Hide comment
@Kalimeiro

Kalimeiro May 3, 2015

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

Kalimeiro commented May 3, 2015

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

@MoonUnit2

This comment has been minimized.

Show comment
Hide comment
@MoonUnit2

MoonUnit2 May 4, 2015

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

MoonUnit2 commented May 4, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ibnuabdirrahim

ibnuabdirrahim May 4, 2015

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

ibnuabdirrahim commented May 4, 2015

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

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost May 4, 2015

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

ghost commented May 4, 2015

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

@Babzsak

This comment has been minimized.

Show comment
Hide comment
@Babzsak

Babzsak May 4, 2015

Same error here.

Ubuntu 14.04
Apache 2.4.7
MySQL 5.5.43
PHP 5.5.9

Babzsak commented May 4, 2015

Same error here.

Ubuntu 14.04
Apache 2.4.7
MySQL 5.5.43
PHP 5.5.9

@bamberino

This comment has been minimized.

Show comment
Hide comment
@bamberino

bamberino May 4, 2015

@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.

bamberino commented May 4, 2015

@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

This comment has been minimized.

Show comment
Hide comment
@benurb

benurb 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.

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

This comment has been minimized.

Show comment
Hide comment
@loloakira

loloakira May 5, 2015

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

loloakira commented May 5, 2015

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

@throker

This comment has been minimized.

Show comment
Hide comment
@throker

throker 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.

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

This comment has been minimized.

Show comment
Hide comment
@Kalimeiro

Kalimeiro May 5, 2015

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.

Kalimeiro commented May 5, 2015

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

This comment has been minimized.

Show comment
Hide comment
@LukasReschke

LukasReschke May 5, 2015

Member

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

Member

LukasReschke commented May 5, 2015

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

@fg-ok

This comment has been minimized.

Show comment
Hide comment
@fg-ok

fg-ok 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!

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

This comment has been minimized.

Show comment
Hide comment
@RobinJ1995

RobinJ1995 Jun 29, 2015

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.

RobinJ1995 commented Jun 29, 2015

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

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Jun 29, 2015

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

Member

DeepDiver1975 commented Jun 29, 2015

@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

This comment has been minimized.

Show comment
Hide comment
@Ninos

Ninos 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..

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

This comment has been minimized.

Show comment
Hide comment
@DeepDiver1975

DeepDiver1975 Jul 8, 2015

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

Member

DeepDiver1975 commented Jul 8, 2015

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

This comment has been minimized.

Show comment
Hide comment
@Ninos

Ninos 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

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

@robertoschwald

This comment has been minimized.

Show comment
Hide comment
@saamo

This comment has been minimized.

Show comment
Hide comment
@saamo

saamo 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

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

This comment has been minimized.

Show comment
Hide comment
@boldandbusted

boldandbusted Oct 8, 2015

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. :)

boldandbusted commented Oct 8, 2015

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Oct 8, 2015

@boldandbusted Just set the correct binlog_format needed by oC

ghost commented Oct 8, 2015

@boldandbusted Just set the correct binlog_format needed by oC

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost 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)

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

This comment has been minimized.

Show comment
Hide comment
@rikur

rikur May 3, 2016

lol such great ux

rikur commented May 3, 2016

lol such great ux

@wedojava

This comment has been minimized.

Show comment
Hide comment
@wedojava

wedojava May 24, 2016

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!!!

wedojava commented May 24, 2016

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

This comment has been minimized.

Show comment
Hide comment
@saamo

saamo May 24, 2016

@wedojava, glad it helped you :-)

saamo commented May 24, 2016

@wedojava, glad it helped you :-)

@ilhanco

This comment has been minimized.

Show comment
Hide comment
@ilhanco

ilhanco Dec 15, 2017

Hello,
I am trying to install shared server version of owncloud on my shared server host ipage. I am getting the same error. Unfortunately i cannot change anything in the configuration since this is a shared hosting.
Any other possible solutions meanwhile?

ilhanco commented Dec 15, 2017

Hello,
I am trying to install shared server version of owncloud on my shared server host ipage. I am getting the same error. Unfortunately i cannot change anything in the configuration since this is a shared hosting.
Any other possible solutions meanwhile?

@MoonUnit2

This comment has been minimized.

Show comment
Hide comment
@MoonUnit2

MoonUnit2 Dec 15, 2017

@ilhanco, if you have already contacted your host and they've said it is impossible to change mysql settings, then I think you are out of luck. I got around this by changing my mysql config, but I also run this on a VPS, not shared hosting.

MoonUnit2 commented Dec 15, 2017

@ilhanco, if you have already contacted your host and they've said it is impossible to change mysql settings, then I think you are out of luck. I got around this by changing my mysql config, but I also run this on a VPS, not shared hosting.

@ilhanco

This comment has been minimized.

Show comment
Hide comment
@ilhanco

ilhanco Dec 15, 2017

ilhanco commented Dec 15, 2017

@Ninos

This comment has been minimized.

Show comment
Hide comment
@Ninos

Ninos Dec 20, 2017

@ilhanco you can try NextCloud (owncloud fork). May there they fixed the bug. Otherwise just create a ticket, may they'll fix it then.

Ninos commented Dec 20, 2017

@ilhanco you can try NextCloud (owncloud fork). May there they fixed the bug. Otherwise just create a ticket, may they'll fix it then.

@ilhanco

This comment has been minimized.

Show comment
Hide comment
@ilhanco

ilhanco Dec 20, 2017

ilhanco commented Dec 20, 2017

@benurb

This comment has been minimized.

Show comment
Hide comment
@benurb

benurb Dec 20, 2017

@Ninos @ilhanco If you would've read the rest of the thread you would know it's neither a bug nor an error. It's just a requirement for a consistent database and thus owncloud/nextcloud both didn't "fix" it.
@ilhanco I would rather recommend searching for a new hosting provider that is more flexible with MySQL configuration.

benurb commented Dec 20, 2017

@Ninos @ilhanco If you would've read the rest of the thread you would know it's neither a bug nor an error. It's just a requirement for a consistent database and thus owncloud/nextcloud both didn't "fix" it.
@ilhanco I would rather recommend searching for a new hosting provider that is more flexible with MySQL configuration.

@Ninos

This comment has been minimized.

Show comment
Hide comment
@Ninos

Ninos Dec 20, 2017

Hey @benurb greetings from Augsburg :D

About the bug, just because it's declared as requirement it's not "fixed". It's definitely a bug, the requirement was set AFTER the devs did not want to fix it :-) Otherwise they should check such requirements on installation process and tell, that owncloud/nextcloud is not usable on such server environment.
I also never heard, that a software is usable only with such mysql log type. I really think the log type is not really needed, just devs didn't want to fix it (low prio).

PS: On shared hosting the mysql configuration is not flexible. You need to trust your hoster to have the correct setting. This is another reason, why it's bad to depend a software on such settings which are only relevant for administrators.

Ninos commented Dec 20, 2017

Hey @benurb greetings from Augsburg :D

About the bug, just because it's declared as requirement it's not "fixed". It's definitely a bug, the requirement was set AFTER the devs did not want to fix it :-) Otherwise they should check such requirements on installation process and tell, that owncloud/nextcloud is not usable on such server environment.
I also never heard, that a software is usable only with such mysql log type. I really think the log type is not really needed, just devs didn't want to fix it (low prio).

PS: On shared hosting the mysql configuration is not flexible. You need to trust your hoster to have the correct setting. This is another reason, why it's bad to depend a software on such settings which are only relevant for administrators.

@ilhanco

This comment has been minimized.

Show comment
Hide comment
@ilhanco

ilhanco Dec 20, 2017

ilhanco commented Dec 20, 2017

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