重启数据库报错MySQL. ERROR! The server quit without updating PID file (/www/mysql/iZ28h
重启报错：Starting LNMP...
Starting nginx...done
Starting MySQL. ERROR! The server quit without updating PID file (/www/mysql/iZ28hs2aieuZ.pid).
错误日志：
2016-10-03 09:00:14 0 /usr/local/mysql/bin/mysqld (mysqld 5.6.29-log) starting as process 3112 ...
2016-10-03 09:00:14 3112 Plugin 'FEDERATED' is disabled.
2016-10-03 09:00:14 3112 InnoDB: Using atomics to ref count buffer pool pages
2016-10-03 09:00:14 3112 InnoDB: The InnoDB memory heap is disabled
2016-10-03 09:00:14 3112 InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-03 09:00:14 3112 InnoDB: Memory barrier is not used
2016-10-03 09:00:14 3112 InnoDB: Compressed tables use zlib 1.2.3
2016-10-03 09:00:14 3112 InnoDB: Using CPU crc32 instructions
2016-10-03 09:00:14 3112 InnoDB: Initializing buffer pool, size = 128.0M
2016-10-03 09:00:14 3112 InnoDB: Completed initialization of buffer pool
2016-10-03 09:00:14 3112 InnoDB: Highest supported file format is Barracuda.
2016-10-03 09:00:14 3112 InnoDB: The log sequence numbers 1626290 and 1626290 in ibdata files do not match the log sequence number 1626300 in the ib_logfiles!
2016-10-03 09:00:14 3112 InnoDB: Database was not shutdown normally!
2016-10-03 09:00:14 3112 InnoDB: Starting crash recovery.
2016-10-03 09:00:14 3112 InnoDB: Reading tablespace information from the .ibd files...
2016-10-03 09:00:14 3112 InnoDB: Attempted to open a previously opened tablespace. Previous tablespace luoxiao/wp_favorites uses space ID: 55 at filepath: ./luoxiao/wp_favorites.ibd. Cannot open tablespace luoxiao/wp_ewwwio_images which uses space ID: 55 at filepath: ./luoxiao/wp_ewwwio_images.ibd
2016-10-03 09:00:14 7fa6f083f740InnoDB: 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 ./luoxiao/wp_ewwwio_images.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.
161003 09:00:14 mysqld_safe mysqld from pid file /www/mysql/iZ28hs2aieuZ.pid ended /etc/my.cnf 里 段里加上innodb_force_recovery=1 然后启动试试
操作前先备份数据库目录
页:
[1]