MySQL 5.7 - BC Break - only_full_group_by mode

  • Bekomme folgende Fehlermeldung angezeigt wenn ich ein Komplett nagelneues Imscp installiert habe und unter denn Kunden account ein Datenbankuser account erstellen möchte.


    Bitte sagt mir was ihr braucht.
    Bekomme folgende email zu geschickt für dieses Problemm


    System immer aktuel
    Debian 8.5
    Mysql server 5.7
    Imscp 1.3.0


    Ein unerwarteter Fehler ist aufgetreten
    Ein unerwarteter Fehler ist aufgetreten. Bitte kontaktieren Sie Ihren Administrator.


    Get the following error message when I have a complete brand new I MSCP installed and for customer account an SQL user want to create account.


    An unexpected error occurred


    An unexpected error occurred. Please contact your administrator.

    my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

    Edited once, last by Speddy ().

  • @Speddy


    Are you sure that you use i-MSCP 1.3.0? In i-MSCP version 1.3.0, there is a configuration parameter added to avoid such a backward compatibility problem with MySQL 5.7.


    Please show us the result of the following comand:

    Code
    1. # cat /etc/mysql/conf.d/imscp.cnf


    Note: Don't forget to hide the password that is in that file.


    In that file, you should have a line such as: https://github.com/i-MSCP/imsc…d/mysql/installer.pm#L237
    If that not the case, this means either that you don't use i-MSCP 1.3.0 or that something went wrong during installation.


    To solve the problem, add that parameter if missing and restart the mysql service:


    Code
    1. # service mysql restart

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

  • @Speddy


    Please, give us the result of the following command:


    Code
    1. cat /etc/imscp/imscp.conf |grep Version


    and please, read my previous post again to know how to solve your problem (I've edited it).

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Code
    1. root@ns367176:~# cat /etc/imscp/imscp.conf |grep Version
    2. Version = Git 1.3.x

    my System :

    - Distribution: Debian | Release: 9.13 | Codename: wheezy
    - i-MSCP Version: i-MSCP 1.5.3| Build: 20181208 | Codename: Ennio Morricone
    - Plugins installed: ClamAV (v. 1.3.0), Mailgraph (v 1.1.1), OpenDKIM (v 2.0.0), SpamAssassin (v 2.0.1)
    - LetsEncrypt (v3.3.0), PhpSwitcher (v 5.0.5), RoundcubePlugins (v 2.0.2)YubiKeyAuth 1.1.0

  • @Speedy


    Ok, I'll re-add the fix for backward compatibility in the 1.3.x branch. It seem that we must audit all our SQL queries before allowing the only_full_group_by SQL mode. I given you the solution already to fix the problem ;)


    Thank you for your report.


    Thread closed.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • Fix re-added in the 1.3.x branch. See https://github.com/i-MSCP/imsc…0ba137587de486728dd2a37d9

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206