ERROR! MySQL server PID file could not be found!

双子宅猫

Centos+LNMP，磁盘空间满了，试图关闭LNMP，删除MYSQL日志（因为以前试过知道日志占用空间大）。关闭LNMP的时候，MYSQL很长时间无响应，最后出现ERROR。
删除了数据库日志后，重启LNMP，MYSQL启动不了。
reboot后出现:ERROR! MySQL server PID file could not be found!

谢谢解答！

licess

按反馈必读提供mysql日志

双子宅猫

150603 17:47:13 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
150603 17:47:13 InnoDB: The InnoDB memory heap is disabled
150603 17:47:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150603 17:47:13 InnoDB: Compressed tables use zlib 1.2.3
150603 17:47:13 InnoDB: Initializing buffer pool, size = 16.0M
150603 17:47:13 InnoDB: Completed initialization of buffer pool
150603 17:47:13 InnoDB: highest supported file format is Barracuda.
150603 17:47:13  InnoDB: Waiting for the background threads to start
150603 17:47:14 InnoDB: 5.5.37 started; log sequence number 1595675
150603 17:47:14 [Note] Recovering after a crash using mysql-bin
150603 17:47:14 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 1764, event_type: 2
150603 17:47:14 [Note] Starting crash recovery...
150603 17:47:14 [Note] Crash recovery finished.
150603 17:47:14 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
150603 17:47:14 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
150603 17:47:14 [Note] Server socket created on IP: '0.0.0.0'.
150603 17:47:14 [Note] Event Scheduler: Loaded 0 events
150603 17:47:14 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.37-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
150603 21:42:45 [Warning] IP address '122.228.236.137' could not be resolved: Name or service not known
150603 22:59:54 [Warning] IP address '219.151.9.44' could not be resolved: Name or service not known
150604  8:46:49 [Warning] IP address '104.149.147.66' could not be resolved: Temporary failure in name resolution
150604  9:20:15 [Warning] IP address '222.186.34.226' could not be resolved: Name or service not known
150604 13:19:27 [Warning] IP address '210.212.98.235' could not be resolved: Name or service not known
150604 19:24:52 [Warning] IP address '60.8.36.75' could not be resolved: Name or service not known
150604 22:27:58 [Warning] IP address '61.240.144.65' could not be resolved: Temporary failure in name resolution
150605  4:14:26 [Warning] IP address '104.217.76.66' could not be resolved: Temporary failure in name resolution
150605  4:29:10 [Warning] IP address '182.92.231.152' could not be resolved: Name or service not known
150606  5:43:48 [Warning] IP address '104.149.147.66' could not be resolved: Temporary failure in name resolution
150606 20:58:53 [Warning] IP address '169.54.233.121' has been resolved to the host name '169.54.233.121-static.reverse.softlayer.com', which resembles IPv4-address itself.
150607  3:31:16 [Warning] IP address '122.224.6.150' could not be resolved: Name or service not known
150608  7:14:10 [Warning] IP address '118.193.131.33' could not be resolved: Name or service not known
150608 13:40:46 [Warning] IP address '58.220.232.43' could not be resolved: Name or service not known
150608 18:04:24 [Warning] IP address '171.11.18.170' has been resolved to the host name '11.171.broad.ha.dynamic.163data.com.cn', which resembles IPv4-address itself.
150608 22:28:28 [Warning] IP address '222.186.34.75' could not be resolved: Name or service not known
150609 11:55:57 [Warning] IP address '180.97.80.253' could not be resolved: Name or service not known
150609 14:35:23 [Warning] IP address '104.247.221.187' could not be resolved: Temporary failure in name resolution
150610 19:55:54 [Warning] IP address '117.21.176.120' could not be resolved: Name or service not known
150610 23:18:23 [Warning] IP address '61.240.144.65' could not be resolved: Temporary failure in name resolution
150611  0:26:32 [Warning] IP address '222.186.21.98' could not be resolved: Name or service not known
150611  5:35:43 [Warning] IP address '117.21.176.17' could not be resolved: Name or service not known
150611  9:13:30 [Warning] IP address '61.240.144.64' could not be resolved: Temporary failure in name resolution
"/usr/local/mysql/var/psychz.net.err" 2206L, 265386C

licess

提供完整日志

双子宅猫

上面贴的就是 /usr/local/mysql/var/psychz.net.err 中的全部内容哦

licess

不要欺负俺学习不好 "/usr/local/mysql/var/psychz.net.err" 2206L, 265386C
上面明明写着有2206行，这才多少行，直接上传该文件

双子宅猫

谢谢！是我不懂。

licess

151014  8:25:02 InnoDB: 5.5.37 started; log sequence number 1632879
/usr/local/mysql/bin/mysqld: File './mysql-bin.000021' not found (Errcode: 2)
151014  8:25:02 [ERROR] Failed to open log (file './mysql-bin.000021', errno 2)
151014  8:25:02 [ERROR] Could not open log file
151014  8:25:02 [ERROR] Can't init tc log
151014  8:25:02 [ERROR] Aborting

应该是误删了mysql-bin.000021的文件
清空mysql-bin.index 然后重启mysql试试

双子宅猫

感激不尽！学习了！谢谢军哥！

iswordfish

谢谢军哥，因为502问题删除了日志，不曾想删错，就不能启动mysql了。
这篇帖子解决了问题。
沟通很顺畅，楼主也很配合，军哥透彻，论坛的好风气。