Problems After Upgrade to 5.6

MySQL & MariaDB Other MySQL® Questions
1

I had problems after upgrading to version 5.6

This is Error Log:

140325 13:29:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/
140325 13:29:40 [ERROR] Can’t find messagefile ‘/usr/share/percona-server/errmsg.sys’
140325 13:29:40 [Note] Plugin ‘FEDERATED’ is disabled.
140325 13:29:40 InnoDB: The InnoDB memory heap is disabled
140325 13:29:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140325 13:29:40 InnoDB: Compressed tables use zlib 1.2.3.4
140325 13:29:40 InnoDB: Using Linux native AIO
140325 13:29:40 InnoDB: Initializing buffer pool, size = 1.0G
140325 13:29:40 InnoDB: Completed initialization of buffer pool
140325 13:29:40 InnoDB: highest supported file format is Barracuda.
140325 13:29:41 InnoDB: Waiting for the background threads to start
140325 13:29:41 InnoDB: Warning: table ‘mysql/innodb_index_stats’
InnoDB: in InnoDB data dictionary has unknown flags 50.
140325 13:29:42 InnoDB: Warning: table ‘mysql/innodb_table_stats’
InnoDB: in InnoDB data dictionary has unknown flags 50.
140325 13:29:42 Percona XtraDB (http://www.percona.com) 5.5.36-34.1-34.1 started; log sequence number 26926465548
140325 13:29:42 [ERROR] Aborting

140325 13:29:42 InnoDB: Starting shutdown…
140325 13:29:47 InnoDB: Shutdown completed; log sequence number 26926465548
140325 13:29:47 [Note]
140325 13:29:47 mysqld_safe mysqld from pid file /var/lib/mysql/mysql.pid ended

After downgrade to previous version, the problem persists.

Ubuntu 12.04.

my.cnf

Generated by Percona Configuration Wizard ([URL]MySQL Tools and Management Software to Perform System Tasks by Percona) version REL5-20120208

[mysql]

CLIENT

port = 3306
socket = /var/lib/mysql/mysql.sock
[mysqld]

GENERAL

user = mysql
default-storage-engine = InnoDB
pid-file = /var/lib/mysql/mysql.pid

MyISAM

key-buffer-size = 32M
myisam-recover-options = FORCE,BACKUP

SAFETY

max-allowed-packet = 16M
max-connect-errors = 1000000

DATA STORAGE

datadir = /var/lib/mysql/

BINARY LOGGING

log-bin = /var/lib/mysql/mysql-bin
expire-logs-days = 7
sync-binlog = 1

CACHES AND LIMITS

tmp-table-size = 32M
max-heap-table-size = 32M
query-cache-type = 1
query-cache-size = 64M
max-connections = 100
thread-cache-size = 16
open-files-limit = 65535
table-definition-cache = 4096
table-open-cache = 4096

INNODB

innodb-flush-method = O_DIRECT
innodb-log-files-in-group = 2
innodb-log-file-size = 128M
innodb-flush-log-at-trx-commit = 1
innodb-file-per-table = 1
innodb-buffer-pool-size = 1G

LOGGING

log-error = /var/lib/mysql/mysql-error.log
log-queries-not-using-indexes = 1
slow-query-log = 1
slow-query-log-file = /var/lib/mysql/mysql-slow.log

2

Hi,

Can you provide the steps how you have upgraded the server? After upgrade to 5.6, have you run mysql_upgrade? can you provide mysql_upgrade log?

3

Hi,

I am seeing the same message in the MySQL log:

I was using the Codership version of MySQL 5.6 (with Galera) and decided to switch to XtraDB cluster…
Before installing XtraDB from the Percona APT repository, I made sure to remove all the previous mysql and galera packages from the system.

After installing XtraDB, those warning messages started appearing in the log. The database seems to otherwise be fine…
I have tried running the mysql_upgrade, and it completed successfully, with no error or warning being shown on the console (but that didn’t fix the warnings from the logs).

What are these warnings? I can’t seem to find any info about what they mean…

Thanks for your help!

-Boris

4

Hi,

So currently which version you are using? 5.5 or 5.6? You issue might be related to this but I’m not sure.
[url]MySQL Bugs: #67179: mysql system tables innodb_table_stats,slave_master_info not accessible on clean

Can you give me the steps how it can be repeatable? if you have better test case then I would suggest to file a bug.
[url]https://bugs.launchpad.net/percona-xtradb-cluster/[/url]

5

[url]https://bugs.launchpad.net/percona-server/+bug/1302882[/url]