Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.6.8, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
-
Docker container
Description
When starting the mariadb 10.6.8 docker container with
, it fails to initialize with--sql-mode=ONLY_FULL_GROUP_BY
ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause
Here a more complete docker run command that we use in Nextcloud server for testing:
docker run -it --rm \
--name mariadb \
-e MYSQL_ROOT_PASSWORD=owncloud \
-e MYSQL_USER=oc_autotest \
-e MYSQL_PASSWORD=owncloud \
-e MYSQL_DATABASE=oc_autotest \
ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \
--sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION
(The docker image is based on the official mariadb10.6.8 docker image and nothing is modified)
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
When starting the mariadb 10.6.8 docker container with --sql-mode=ONLY_FULL_GROUP_BY`, it fails to initialize with `ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause`.
Here a more complete docker run command that we use in Nextcloud server for testing: ``` docker run -it --rm \ --name mariadb \ -e MYSQL_ROOT_PASSWORD=owncloud \ -e MYSQL_USER=oc_autotest \ -e MYSQL_PASSWORD=owncloud \ -e MYSQL_DATABASE=oc_autotest \ ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \ --sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION ``` |
When starting the mariadb 10.6.8 docker container with {quote}--sql-mode=ONLY_FULL_GROUP_BY{quote}, it fails to initialize with {quote}ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause{quote}
Here a more complete docker run command that we use in Nextcloud server for testing: {quote}docker run -it --rm \ --name mariadb \ -e MYSQL_ROOT_PASSWORD=owncloud \ -e MYSQL_USER=oc_autotest \ -e MYSQL_PASSWORD=owncloud \ -e MYSQL_DATABASE=oc_autotest \ ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \ --sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION{quote} |
| Description |
When starting the mariadb 10.6.8 docker container with {quote}--sql-mode=ONLY_FULL_GROUP_BY{quote}, it fails to initialize with {quote}ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause{quote}
Here a more complete docker run command that we use in Nextcloud server for testing: {quote}docker run -it --rm \ --name mariadb \ -e MYSQL_ROOT_PASSWORD=owncloud \ -e MYSQL_USER=oc_autotest \ -e MYSQL_PASSWORD=owncloud \ -e MYSQL_DATABASE=oc_autotest \ ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \ --sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION{quote} |
When starting the mariadb 10.6.8 docker container with {quote}--sql-mode=ONLY_FULL_GROUP_BY{quote}, it fails to initialize with {quote}ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause{quote}
Here a more complete docker run command that we use in Nextcloud server for testing: {quote}docker run -it --rm \ --name mariadb \ -e MYSQL_ROOT_PASSWORD=owncloud \ -e MYSQL_USER=oc_autotest \ -e MYSQL_PASSWORD=owncloud \ -e MYSQL_DATABASE=oc_autotest \ ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \ --sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION{quote} (The docker image is based on the official mariadb10.6.8 docker image and nothing is modified) |
| Component/s | Time zones [ 10108 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.7 [ 24805 ] | |
| Fix Version/s | 10.8 [ 26121 ] | |
| Fix Version/s | 10.9 [ 26905 ] | |
| Fix Version/s | 10.10 [ 27530 ] | |
| Affects Version/s | 10.6 [ 24028 ] | |
| Affects Version/s | 10.7 [ 24805 ] | |
| Affects Version/s | 10.8 [ 26121 ] | |
| Affects Version/s | 10.9 [ 26905 ] | |
| Affects Version/s | 10.10 [ 27530 ] | |
| Assignee | Daniel Black [ danblack ] | |
| Priority | Critical [ 2 ] | Blocker [ 1 ] |
| Status | Open [ 1 ] | Confirmed [ 10101 ] |
| Labels | regression |
Thanks szaimen for the bug report.
I added a workaround that will be included in the current q3-2022 set of release soon.
Non-container users can use the same workaround. Being a blocker bug this will be corrected in the next server release.
| Assignee | Daniel Black [ danblack ] | Sergei Golubchik [ serg ] |
| Link | This issue causes MENT-1621 [ MENT-1621 ] |
| Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Stalled [ 10000 ] |
| Assignee | Sergei Golubchik [ serg ] | Oleksandr Byelkin [ sanja ] |
| Status | Stalled [ 10000 ] | In Review [ 10002 ] |
| Assignee | Oleksandr Byelkin [ sanja ] | Sergei Golubchik [ serg ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
No, the issue isn't closed yet. The new release was an out-of-schedule release to fix critical data corruption regressions. This fix didn't make it there, it'll be in the next scheduled release.
| Fix Version/s | 10.6.11 [ 28441 ] | |
| Fix Version/s | 10.7.7 [ 28442 ] | |
| Fix Version/s | 10.8.6 [ 28443 ] | |
| Fix Version/s | 10.9.4 [ 28444 ] | |
| Fix Version/s | 10.10.2 [ 28410 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.7 [ 24805 ] | |
| Fix Version/s | 10.8 [ 26121 ] | |
| Fix Version/s | 10.9 [ 26905 ] | |
| Fix Version/s | 10.10 [ 27530 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
Thanks for the report.
The problem is not limited to docker containers, general timezone initialization fails the same way. Apparently the failure was brought by
commit 13e77930e615f05cc74d408110e887b00e1abcc9Author: Daniel BlackDate: Wed Apr 6 13:12:21 2022 +1000MDEV-28263: mariadb-tzinfo-to-sql improve wsrep and binlog caseswhich introduced the query in question.