MariaDB failing to import backup.
by jmgibson1981 from LinuxQuestions.org on (#59MR9)
Ubuntu 20.04 Docker container in an Ubuntu 20.04 LXD Container on an Ubuntu 18.04 host.
I've been moving myself into Docker containers recently. Last night I was experimenting with a container for MariaDB. On import I got this message.
Code:$ zcat mydatabases.2020.10.28.07.21.sql.gz | docker exec -i mariadb mysql
ERROR 1556 (HY000) at line 5331: You can't use locks with log tables
read unix @->/run/docker.sock: read: connection reset by peerWhen this happens the DB import fails. If I enter the container and run Code:show databases; from mysql it's missing a few entries that should be there.
This is pulling from my server. The issue is I have been using this same backup script, and have done several restores due to experimentation, or just stupidity and had no trouble for a few years now. I actually re-imported to my host just a few days ago when I had an issue with mythtv being able to hit the docker container.
Here is my script.
Code:sql_backup_func() {
SQLBACKDIR="$POOLLOC"/backups/mysqldump
if [ "$USER" = root ] ; then
zcat "$(find "$SQLBACKDIR"/ -type f | tail -n 1)" | mysql
else
mysqldump \
--user=backup \
--password=backup \
--single-transaction \
--all-databases | gzip > "$SQLBACKDIR"/mydatabases."$NOW".sql.gz
find "$SQLBACKDIR"/ -type f -mtime +5 -exec rm {} \;
fi
}I've tried bare metal on my desktop with the same results. I'm concerned because at the moment while my DB is running just fine on my main server host os, if it goes down I don't seem to be able to restore it from my backups.
Added rsyslog to my docker container. This is the whole of the log.
Code:Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: activation of module imklog failed [v8.2001.0 try https://www.rsyslog.com/e/2145 ]
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: rsyslogd's groupid changed to 102
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: rsyslogd's userid changed to 102
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="20" x-info="https://www.rsyslog.com"] >
Oct 28 14:52:22 8ede8a0c64c3 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] /usr/sbin/mysqld (mysqld 10.3.25-MariaDB-0ubuntu0.20.04.1) starting>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Using Linux native AIO
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Uses event mutexes
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Number of pools: 1
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Using SSE2 crc32 instructions
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1,>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Completed initialization of buffer pool
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner th>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing t>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Waiting for purge to start
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: 10.3.25 started; log sequence number 1625443; transaction i>
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Plugin 'FEEDBACK' is disabled.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: Buffer pool(s) load completed at 201028 14:52:23
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Server socket created on IP: '0.0.0.0'.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Reading of all Master_info entries succeeded
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Added new Master_info '' to hash table
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] /usr/sbin/mysqld: ready for connections.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: Version: '10.3.25-MariaDB-0ubuntu0.20.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 >
Oct 28 14:52:23 8ede8a0c64c3 /etc/mysql/debian-start[242]: Upgrading MySQL tables if necessary.
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Looking for 'mysql' as: /usr/bin/mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 1/7: Checking and upgrading mysql database
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.column_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.columns_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.db OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.event OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.func OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.gtid_slave_pos OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_category OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_keyword OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_relation OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_topic OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.host OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.index_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.innodb_index_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.innodb_table_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.plugin OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.proc OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.procs_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.proxies_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.roles_mapping OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.servers OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.table_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.tables_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_leap_second OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_name OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_transition OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_transition_type OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.transaction_registry OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.user OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 2/7: Installing used storage engines... Skipped
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 3/7: Fixing views
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 4/7: Running 'mysql_fix_privilege_tables'
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 5/7: Fixing table and database names
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 6/7: Checking and upgrading tables
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 7/7: Running 'FLUSH PRIVILEGES'
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[278]: Checking for insecure root accounts.
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[282]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Oct 28 14:53:36 8ede8a0c64c3 mysqld: 2020-10-28 14:53:36 53 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgradeThe log goes to the end with the last line many times over and over. The /var/log/mysql/errors.log is empty.
*EDIT* Just for good measure I just ran a mysql_upgrade --force on my main server, then a fresh db dump. Same issue on a clean fresh docker container with a brand new volume for storage.
*EDIT 2* Thought of trying an 18.04 Docker. Same result again.
*EDIT 3* Further testing. An 18.04 LXD container imported with no trouble. Maybe something to do with Docker inside of an LXD container?
*EDIT 4* Failed import to a 20.04 LXD container. Same error as above.
Somewhere the 20.04 change is the issue, both hosting docker or the host itself.
*EDIT* Something to do with 20.04 definitely. My final experiment just now involved my laptop which is running 20.04. Installed mariadb-server from the repos and got the same result on import. I don't think it's the mariadb package though because it happens inside of an 18.04 docker container on a 20.04 lxd container which has no mariadb packages installed by me. Now it happens on a bare metal 20.04 fresh installation.


I've been moving myself into Docker containers recently. Last night I was experimenting with a container for MariaDB. On import I got this message.
Code:$ zcat mydatabases.2020.10.28.07.21.sql.gz | docker exec -i mariadb mysql
ERROR 1556 (HY000) at line 5331: You can't use locks with log tables
read unix @->/run/docker.sock: read: connection reset by peerWhen this happens the DB import fails. If I enter the container and run Code:show databases; from mysql it's missing a few entries that should be there.
This is pulling from my server. The issue is I have been using this same backup script, and have done several restores due to experimentation, or just stupidity and had no trouble for a few years now. I actually re-imported to my host just a few days ago when I had an issue with mythtv being able to hit the docker container.
Here is my script.
Code:sql_backup_func() {
SQLBACKDIR="$POOLLOC"/backups/mysqldump
if [ "$USER" = root ] ; then
zcat "$(find "$SQLBACKDIR"/ -type f | tail -n 1)" | mysql
else
mysqldump \
--user=backup \
--password=backup \
--single-transaction \
--all-databases | gzip > "$SQLBACKDIR"/mydatabases."$NOW".sql.gz
find "$SQLBACKDIR"/ -type f -mtime +5 -exec rm {} \;
fi
}I've tried bare metal on my desktop with the same results. I'm concerned because at the moment while my DB is running just fine on my main server host os, if it goes down I don't seem to be able to restore it from my backups.
Added rsyslog to my docker container. This is the whole of the log.
Code:Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: activation of module imklog failed [v8.2001.0 try https://www.rsyslog.com/e/2145 ]
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: rsyslogd's groupid changed to 102
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: rsyslogd's userid changed to 102
Oct 28 14:52:22 8ede8a0c64c3 rsyslogd: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="20" x-info="https://www.rsyslog.com"] >
Oct 28 14:52:22 8ede8a0c64c3 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] /usr/sbin/mysqld (mysqld 10.3.25-MariaDB-0ubuntu0.20.04.1) starting>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Using Linux native AIO
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Uses event mutexes
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Number of pools: 1
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Using SSE2 crc32 instructions
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1,>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Completed initialization of buffer pool
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner th>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing t>
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Oct 28 14:52:22 8ede8a0c64c3 mysqld: 2020-10-28 14:52:22 0 [Note] InnoDB: Waiting for purge to start
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: 10.3.25 started; log sequence number 1625443; transaction i>
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Plugin 'FEEDBACK' is disabled.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] InnoDB: Buffer pool(s) load completed at 201028 14:52:23
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Server socket created on IP: '0.0.0.0'.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Reading of all Master_info entries succeeded
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] Added new Master_info '' to hash table
Oct 28 14:52:23 8ede8a0c64c3 mysqld: 2020-10-28 14:52:23 0 [Note] /usr/sbin/mysqld: ready for connections.
Oct 28 14:52:23 8ede8a0c64c3 mysqld: Version: '10.3.25-MariaDB-0ubuntu0.20.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 >
Oct 28 14:52:23 8ede8a0c64c3 /etc/mysql/debian-start[242]: Upgrading MySQL tables if necessary.
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Looking for 'mysql' as: /usr/bin/mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 1/7: Checking and upgrading mysql database
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.column_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.columns_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.db OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.event OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.func OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.gtid_slave_pos OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_category OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_keyword OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_relation OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.help_topic OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.host OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.index_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.innodb_index_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.innodb_table_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.plugin OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.proc OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.procs_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.proxies_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.roles_mapping OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.servers OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.table_stats OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.tables_priv OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_leap_second OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_name OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_transition OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.time_zone_transition_type OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.transaction_registry OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql.user OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 2/7: Installing used storage engines... Skipped
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 3/7: Fixing views
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 4/7: Running 'mysql_fix_privilege_tables'
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 5/7: Fixing table and database names
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: mysql
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 6/7: Checking and upgrading tables
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Processing databases
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: information_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: performance_schema
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: Phase 7/7: Running 'FLUSH PRIVILEGES'
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[245]: OK
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[278]: Checking for insecure root accounts.
Oct 28 14:52:24 8ede8a0c64c3 /etc/mysql/debian-start[282]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Oct 28 14:53:36 8ede8a0c64c3 mysqld: 2020-10-28 14:53:36 53 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name. Please run mysql_upgradeThe log goes to the end with the last line many times over and over. The /var/log/mysql/errors.log is empty.
*EDIT* Just for good measure I just ran a mysql_upgrade --force on my main server, then a fresh db dump. Same issue on a clean fresh docker container with a brand new volume for storage.
*EDIT 2* Thought of trying an 18.04 Docker. Same result again.
*EDIT 3* Further testing. An 18.04 LXD container imported with no trouble. Maybe something to do with Docker inside of an LXD container?
*EDIT 4* Failed import to a 20.04 LXD container. Same error as above.
Somewhere the 20.04 change is the issue, both hosting docker or the host itself.
*EDIT* Something to do with 20.04 definitely. My final experiment just now involved my laptop which is running 20.04. Installed mariadb-server from the repos and got the same result on import. I don't think it's the mariadb package though because it happens inside of an 18.04 docker container on a 20.04 lxd container which has no mariadb packages installed by me. Now it happens on a bare metal 20.04 fresh installation.