Dana Williams asked:
I could use some help figuring out why upgrading from MySQL 5.6 to MariaDB 10 On Centos 6 is proving so difficult.
Below are the steps I am using followed by the error
cat /etc/centos-release
CentOS release 6.8 (Final)
mysql -V
mysql Ver 14.14 Distrib 5.6.35, for Linux (x86_64) using EditLine wrapper
yum -y update
mysqldump --all-databases -p > /tmp/backupdatabase.sql
cp /etc/my.cnf /tmp/my.cnf.bak
service mysqld stop
chkconfig mysqld off
yum remove mysql* mysql-server mysql-devel mysql-libs
edit /etc/yum.repos.d/mariadb.repo to point to MariaDB 10 source
yum clean all
yum install MariaDB-server galera MariaDB-client MariaDB-shared MariaDB-backup MariaDB-common
Everything looks fine until this point then:
service mysql start
service mysql start
Starting MariaDB.190801 13:39:12 mysqld_safe Logging to '/var/lib/mysql/designtv.designtv.net.err'.
190801 13:39:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
...../etc/init.d/mysql: line 260: kill: (3056) - No such process
Error Log
190801 14:00:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
190801 14:00:25 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys'
/usr/libexec/mysqld: Unknown error 1146
190801 14:00:25 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
190801 14:00:25 InnoDB: Initializing buffer pool, size = 8.0M
190801 14:00:25 InnoDB: Completed initialization of buffer pool
190801 14:00:25 InnoDB: Started; log sequence number 0 44233
190801 14:00:25 [ERROR] Aborting
190801 14:00:25 InnoDB: Starting shutdown...
190801 14:00:30 InnoDB: Shutdown completed; log sequence number 0 44233
190801 14:00:30 [Note]
190801 14:00:30 mysqld_safe mysqld from pid file /var/lib/mysql/designtv.designtv.net.pid ended
“/var/lib/mysql/designtv.designtv.net.err” is world readable
ls -la /usr/share/mysql/english/errmsg.sys
-rw-r--r-- 1 root root 61764 Jan 29 2019 /usr/share/mysql/english/errmsg.sys
“[ERROR] Can’t open the mysql.plugin table. Please run mysql_upgrade to create it.”
I can’t run mysql_ugrade until the server is running.
My answer:
It looks like you may still have files left over from the previous MySQL installation. There should not be a path /usr/libexec/mysqld
, for instance.
Additionally, you should call the service as mariadb
, not mysql
, e.g.: systemctl start mariadb
. (And try to stop using the deprecated service
command, as it will go away eventually.)
View the full question and any other answers on Server Fault.
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.