Huge MySQL Problem - Printable Version
+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: Huge MySQL Problem (/showthread.php?tid=408831)
+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: Huge MySQL Problem (/showthread.php?tid=408831)
____ - Mellnik - 19.01.2013
____
Re: Huge MySQL Problem - Memoryz - 19.01.2013
Quote:
|
This could be very bad, 2013 means that the thread servicing the mysqldump process has died. This could be because the InnoDB engine on the server has detected an error while reading the database file for you database. As mysqldump has to read all the pages for all of your database to make the backup it is likely to trigger any latent corruption that your application may avoid during it day to day activity. If you run your mysql command and it reports that your connection id is a low number then you server has probably restarted itself. You should check your mysqld.log immediately to find out why. |
AW: Huge MySQL Problem - Mellnik - 19.01.2013
Thanks! So altering mysql engine to MyISAM will fix it?
The mysqld.log is empty because logging isnt enabled.