[email?protected] dmp]# /etc/init.d/mysqld start

Starting MySQL. ERROR! The server quit without updating PID file (/opt/mysql/data/15-144.pid).

2、查看mysql 日志

180625 16:08:17 mysqld_safe Starting mysqld daemon with databases from /opt/mysql/data

2018-06-25 16:08:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2018-06-25 16:08:18 0 [Note] /opt/mysql/bin/mysqld (mysqld 5.6.33) starting as process 22431 ...

2018-06-25 16:08:18 22431 [Note] Plugin ‘FEDERATED‘ is disabled.

2018-06-25 16:08:18 22431 [Note] InnoDB: Using atomics to ref count buffer pool pages

2018-06-25 16:08:18 22431 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-25 16:08:18 22431 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-25 16:08:18 22431 [Note] InnoDB: Memory barrier is not used

2018-06-25 16:08:18 22431 [Note] InnoDB: Compressed tables use zlib 1.2.3

2018-06-25 16:08:18 22431 [Note] InnoDB: Using Linux native AIO

2018-06-25 16:08:18 22431 [Note] InnoDB: Using CPU crc32 instructions

2018-06-25 16:08:18 22431 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2018-06-25 16:08:18 22431 [Note] InnoDB: Completed initialization of buffer pool

2018-06-25 16:08:18 22431 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-25 16:08:18 22431 [Note] InnoDB: Log scan progressed past the checkpoint lsn 281721748253

2018-06-25 16:08:18 22431 [Note] InnoDB: Database was not shutdown normally!

2018-06-25 16:08:18 22431 [Note] InnoDB: Starting crash recovery.

2018-06-25 16:08:18 22431 [Note] InnoDB: Reading tablespace information from the .ibd files...

2018-06-25 16:08:18 22431 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace zabbix/items_applications uses space ID: 994 at filepath: ./zabbix/items_applications.ibd. Cannot open tablespace dmp/app_model_reuse which uses space ID: 994 at filepath: ./dmp/app_model_reuse.ibd

2018-06-25 16:08:18 7fc2adb7f740 InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

InnoDB: Error: could not open single-table tablespace file ./dmp/app_model_reuse.ibd

InnoDB: We do not continue the crash recovery, because the table may become

InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.

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.

180625 16:08:18 mysqld_safe mysqld from pid file /opt/mysql/data/15-144.pid ended

3、解決方案

添加配置/etc/my.cnf

innodb_force_recovery =1

文件解決

原文：http://blog.51cto.com/13833333/2132541

總結

以上是生活随笔為你收集整理的mysql数据库未启动失败_mysql数据库启动失败的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。