The server quit without updating PID file (/usr/local/mysql/data/mysql.pid
这个错误几乎包揽了mysql的所有启动报错；
查一下sql 错误日志
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
160721 12:14:43 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysql.pid ended
首先InnoDB；
在者
If the table is not needed, or you can restore it from a backup,
then you can remove the .ibd file, and InnoDB will do a normal
crash recovery and ignore that table.
由于我用一个innodb表引擎的数据库 覆盖了另外一个无用的数据库文件；
rm -rf 错误的table