Hot answers tagged crash
I just had the same problem, this was fixed by issuing a command, assuming mysql data dir is on /var/lib/mysql/mysql myisamchk -q -r /var/lib/mysql/mysql/proc Source : http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html
No, rollbacks cannot be done in the background. Both that and the double write checks have to be done before accepting connections again (meaning that if you kill it, you will have to start again on restart). REDO process, however, can and is done in the background. What you can do is kill mysql (again) and restart it skipping that step: /etc/init.d/mysqld ...
I take it you are using REPAIR TABLE by hand. I also take it your are doing an automatic table repair for MyISAM. (You have to remove or comment out the option of my.cnf to disable automatic MyISAM table repair). You can actually repair the table without using MySQL but mysqld cannot be accessing it. How? You have to use the offline utility myisamchk ...
In the end, it was only after changing my hosting plan (and moving away from cPanel, which seemed to obscure some of the logging) that I was able to see the issue. Turns out that from time to time, memory usage would spike (I'm guessing that this was because of a dramatic spike in apache child processes) and this would cause memory pressure. The ...
Only top voted, non community-wiki answers of a minimum length are eligible