Your message dated Sat, 19 Feb 2022 17:12:28 -0800 with message-id <caou6tad47ak3rkmov4n1nj+df5aqzp1-1fgajcorupxxol2...@mail.gmail.com> and subject line Re: [debian-mysql] Bug#996389: mariadb-server: FATAL ERROR: Upgrade failed has caused the Debian Bug report #996389, regarding mariadb-server: FATAL ERROR: Upgrade failed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 996389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996389 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mariadb-server Version: 1:10.5.12-0+deb11u1 Severity: normal Tags: l10n patch Dear Maintainer, Automatic upgrade of MySQL tables fails if there're databases and/or tables with non-ASCII names. See also #995066. # cat /var/log/syslog ... Oct 10 10:14:52 neva systemd[1]: Started MariaDB 10.5.12 database server. Oct 10 10:14:52 neva /etc/mysql/debian-start[4171797]: Upgrading MySQL tables if necessary. ... Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: Phase 2/7: Installing used storage engines... Skipped Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: Phase 3/7: Fixing views Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: Running 'mysqlcheck' with connection arguments: --socket='/run/mysqld/mysqld.sock' --host='localhost' --socket='/var/run/mysqld/mysqld.sock' --host='localhost' --socket='/var/run/mysqld/mysqld.sock' Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: Processing databases Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: information_schema Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: mysql Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: mysql.user OK Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: performance_schema ... Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: wordpress-www Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: ??? ???? Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: /usr/bin/mysqlcheck: Got error: 1049: Unknown database '??? ????' when selecting the database Oct 10 10:14:52 neva /etc/mysql/debian-start[4171800]: FATAL ERROR: Upgrade failed Oct 10 10:14:52 neva /etc/mysql/debian-start[4171834]: Checking for insecure root accounts. Oct 10 10:14:52 neva /etc/mysql/debian-start[4171841]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Oct 10 10:14:57 neva /etc/mysql/debian-start[4173463]: WARNING: mysqlcheck has found corrupt tables Oct 10 10:14:57 neva /etc/mysql/debian-start[4173463]: ERROR 1146 (42S02) at line 1: Table '??? ????.??? ??????' doesn't exist Oct 10 10:14:57 neva /etc/mysql/debian-start[4173463]: ERROR 1146 (42S02) at line 1: Table '??? ????.GDP' doesn't exist -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mariadb-server depends on: ii mariadb-server-10.5 1:10.5.12-0+deb11u1 mariadb-server recommends no packages. mariadb-server suggests no packages. -- no debconf information--- /usr/share/mysql/debian-start.inc.sh 2021-09-25 16:15:00.757459188 +0300 +++ /usr/share/mysql/debian-start.inc.sh 2021-10-13 17:52:27.289695579 +0300 @@ -58,7 +58,7 @@ # Filter all "duplicate column", "duplicate key" and "unknown column" # errors as the script is designed to be idempotent. - LC_ALL=C $MYUPGRADE \ + $MYUPGRADE \ 2>&1 \ | egrep -v '^(1|@had|ERROR (1051|1054|1060|1061|1146|1347|1348))' \ | logger -p daemon.warn -i -t$0
--- End Message ---
--- Begin Message ---Hello Alexander! It seems that this issue has no actionable items on how to improve the user experience for everybody. Thus I am closing this issue as there are no actions to take about it. If you later come up with improvements to the MariaDB packaging in Debian, please consider contributing by submitting a Merge Request. https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian Thanks!
--- End Message ---
