[[email protected] ~]#/data/3308/mysql start
Starting MySQL ...
[Email protected] ~]# ll/data/3308/
Total Dosage 72
Drwxr-xr-x 3 MySQL root 4096 July 10:38 data
-rw-r--r--1 root root 1899 July 16:01 my.cnf
-rwx--x--x 1 mysql mysql 1307 July 15:06 MySQL
-RW-RW----1 MySQL mysql 126 July 16:03 mysql-bin.000001
-RW-RW----1 MySQL mysql 224 July 10:38 mysql-bin.index
-RW-RW----1 MySQL mysql 5 July 10:38 mysqld.pid
-rw-r-----1 mysql root 19423 July 10:38 mysql_oldboy3308.err
srwxrwxrwx 1 mysql mysql 0 July 10:38 mysql.sock
Because we may again shut down the virtual machine before shutting down the multi-instance database, so that our multi-instance database, although forced to shut down, but the remnants of the Mysql.sock file should be deleted, when you start the next boot multi-instance database, you can not start a multi-instance database.
[[email protected] 3308]#/data/3308/mysql start
MySQL is running ...
[Email protected] 3308]# Netstat-lntup|grep 330
TCP 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1196/mysql
This time we need to/data/3308/inside the Mysql.sock file directly deleted, you can start MySQL!
Direct shutdown of Linux, causing multiple instances of MySQL to fail to start
