I found the cause of this issue was from all the diskspace being used but clearing it was not enough. I guess the tables became inconsistent when space ran out and myisamchk is what fixed the rest.
service mysqld restart
ERROR! MySQL manager or server PID file could not be found!
....................................................................................... ERROR! Manager of pid-file quit without updating file.
service mysqld status
/etc/init.d/mysqld: line 409: test: too many arguments
ERROR! MySQL is running but PID file could not be found
in 60 secs
110118 23:43:20 [ERROR] /usr/sbin/mysqld: Disk is full writing './blog/wp_comments.MYD' (Errcode: 122). Waiting for someone to free space... Retry in 60 secs
110118 23:53:20 [ERROR] /usr/sbin/mysqld: Disk is full writing './blog/wp_comments.MYD' (Errcode: 122). Waiting for someone to free space... Retry in 60 secs
Even with free space it won't start:
ERROR! MySQL manager or server PID file could not be found!
Starting MySQL.................................................................................................... ERROR! Manager of pid-file quit without updating file.
[root@server mysql]# service mysqld status
/etc/init.d/mysqld: line 409: test: too many arguments
ERROR! MySQL is running but PID file could not be found
Solution repair tables with myisamchk
cd /var/lib/mysql
myisamchk *
mysql, server, pid, updating, diskspace, clearing, inconsistent, myisamchk, mysqld, restart, etc, init, arguments, secs, usr, sbin, disk, blog, wp_comments, myd, errcode, retry, repair, var, lib,