Centos 6.3 Problems encountered in upgrading Mysql 5.1.61 to mysql 5.6.19 and solutions

Environment: mysql - 5.1.61

Operating system :Cent-os6.3

Purpose: Upgrade to mysql 5.6.19

First of all,yum is not feasible, because the yum source has not been updated, I have used the source of 163 netease, but it still doesn't work. The latest version is still not 5.6.

Go to the website to download address: http: / / dev mysql. com/downloads mysql /

I am cent os and Selected Red Hat Enterprise Linux.

Since the system is i686, i686 version was selected

If you just load mysql, you can choose ES37en-ES38en, and I downloaded the entire package.

The server then installs the rpm package

rpm -ivh MySQL-server-5.6.19-1.el6.i686

Error. file/usr/share/mysql charsets/README from install of MySQL - server - 5.6.10-1. linux_glibc2. 5. i386conflicts with file from package mysql - libs - 5.1.61-4. el6. i686

mysql-server.rpm packet and ES75en-ES76en packet conflict...

Very simple, remove ES79en-ES80en package, anyway 5.1 version.

Then continue to install ES83en-ES84en and the installation is successful

Then start the mysql service.

Error: Connection error: Can 't connect to local MySQL server through socket'/var/lib/mysql/mysql sock 'mysql sock

Reviewed the mysql log, because no files/var/run/mysql/xxx looked at 1, original/var/run/mysql didn't folder, then set up, and then fix.

Don't know how the password, then use mysql_safe to operation, change the password. See https: / / www ofstack. com article / 16726. htm

Then change the password, log in, import data, prompt me to change the mysql password first, ok.

After the modification, import the database. Forget what mistake...

Then when importing code import under setting 1.. Fix...

Next, it is found that ES140en-mysql does not exist. Under yum1, the connection package of ES143en-ES144en is needed again. The bag clashed with me again.

Then install MySQL-ES148en-ES149en-5.6.19-1.el6.i686. done

php-mysql is installed.

Remember this article is the same as the current account 1.. No specific reasons for the problem... Because it was urgent, no details of the error were recorded...

Summarize experience, record next time