maria-developers team mailing list archive

[Otto Kekäläinen <otto@xxxxxxxxx>]

Hello!

When testing mysql 5.6 -> mariadb 10.0 I noticed that syslog looks like below.

Are any of these errors anything we need to care about?

The databases where completely vanilla out-of-the-box, so I imagine
all users doing the same upgrade will experience the same error
messages. I didn't notice that it would have any actual effect on
anything, these error messages are just a QA signal.


Jan 11 00:13:42 sid mysqld[22723]:
_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
Jan 11 00:13:42 sid mysqld[22723]: 160111  0:13:42 [ERROR] mysqld:
Event Scheduler: An error occurred when initializing system tables.
Disabling the Event Scheduler.
Jan 11 00:13:42 sid mysqld[22723]: 2016-01-11 00:13:42 7f6caa5ba700
InnoDB: Error: Column last_update in table
"mysql"."innodb_table_stats" is BINARY(4) NOT NULL but should be INT
NOT NULL (type mismatch).
Jan 11 00:13:42 sid mysqld[22723]: 2016-01-11 00:13:42 7f6caa5ba700
InnoDB: Error: Fetch of persistent statistics requested for table
"mysql"."gtid_slave_pos" but the required system tables
mysql.innodb_table_stats and mysql.innodb_index_stats are not present
or have unexpected structure. Using transient stats instead.
Jan 11 00:13:43 sid mysqld[22723]: 160111  0:13:43 [Note]
/usr/sbin/mysqld: ready for connections.
Jan 11 00:13:43 sid mysqld[22723]: Version: '10.0.23-MariaDB-2'
socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian unstable
Jan 11 00:13:43 sid mysql[22552]: Starting MariaDB database server: mysqld.
Jan 11 00:13:43 sid systemd[1]: Started LSB: Start and stop the mysql
database server daemon.
Jan 11 00:13:43 sid /etc/mysql/debian-start[22771]: Upgrading MySQL
tables if necessary.
Jan 11 00:14:00 sid mysqld[22723]: 2016-01-11 00:14:00 7f6caa5ba700
InnoDB: Error: Column last_update in table
"mysql"."innodb_table_stats" is BINARY(4) NOT NULL but should be INT
NOT NULL (type mismatch).