[Maria-developers] Log warnings when upgrading from mysql 5.6 -> mariadb 10.0
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).
Hi, These warnings are printed because some of the system table definitions have been changed, you should run mysql_upgrade and restart should be again more silent. R: Jan On Mon, Jan 11, 2016 at 8:56 AM, Otto Kekäläinen <otto@seravo.fi> wrote:
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).
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
2016-01-11 9:25 GMT+02:00 Jan Lindström <jan.lindstrom@mariadb.com>:
These warnings are printed because some of the system table definitions have been changed, you should run mysql_upgrade and restart should be again more silent.
mysql_upgrade is always run automatically and the next restart was silent I just wanted to check to be sure that these indeed can be ignored.
From user point of view it would be nicer if the upgrade ran automatically before any of the mysqld starts so that there would not be any "alarming" errors in the log, but that is very minor.
Thanks
Am 11.01.2016 um 09:39 schrieb Otto Kekäläinen:
2016-01-11 9:25 GMT+02:00 Jan Lindström <jan.lindstrom@mariadb.com>:
These warnings are printed because some of the system table definitions have been changed, you should run mysql_upgrade and restart should be again more silent.
mysql_upgrade is always run automatically and the next restart was silent
I just wanted to check to be sure that these indeed can be ignored. From user point of view it would be nicer if the upgrade ran automatically before any of the mysqld starts so that there would not be any "alarming" errors in the log, but that is very minor
chicken/egg problem mysql_upgrade can't run before the daemon is started
Hi, I agree with you, I do not fully understand why mysql_upgrade is separate program, at startup mysqld should check current dictionary version and if it does not match server version call function to upgrade the system tables automatically. Created https://mariadb.atlassian.net/browse/TODO-776 for this. R: Jan On Mon, Jan 11, 2016 at 10:39 AM, Otto Kekäläinen <otto@seravo.fi> wrote:
2016-01-11 9:25 GMT+02:00 Jan Lindström <jan.lindstrom@mariadb.com>:
These warnings are printed because some of the system table definitions have been changed, you should run mysql_upgrade and restart should be again more silent.
mysql_upgrade is always run automatically and the next restart was silent
I just wanted to check to be sure that these indeed can be ignored. From user point of view it would be nicer if the upgrade ran automatically before any of the mysqld starts so that there would not be any "alarming" errors in the log, but that is very minor.
Thanks
I did not remember to make it totally public, modified version: https://mariadb.atlassian.net/browse/MDEV-9394 On Mon, Jan 11, 2016 at 12:51 PM, Jan Lindström <jan.lindstrom@mariadb.com> wrote:
Hi,
I agree with you, I do not fully understand why mysql_upgrade is separate program, at startup mysqld should check current dictionary version and if it does not match server version call function to upgrade the system tables automatically. Created https://mariadb.atlassian.net/browse/TODO-776 for this.
R: Jan
On Mon, Jan 11, 2016 at 10:39 AM, Otto Kekäläinen <otto@seravo.fi> wrote:
2016-01-11 9:25 GMT+02:00 Jan Lindström <jan.lindstrom@mariadb.com>:
These warnings are printed because some of the system table definitions have been changed, you should run mysql_upgrade and restart should be again more silent.
mysql_upgrade is always run automatically and the next restart was silent
I just wanted to check to be sure that these indeed can be ignored. From user point of view it would be nicer if the upgrade ran automatically before any of the mysqld starts so that there would not be any "alarming" errors in the log, but that is very minor.
Thanks
participants (3)
-
Jan Lindström -
Otto Kekäläinen -
Reindl Harald