Recently been attacked by

"Can't create/write to file '/tmp/#sql_28e2_0.MYI' (Errcode: 13)"?

Then its a simple fix, please DELETE (backup first) your SOURCE files that talk to the MySQL database, and re-upload them

This will purge them from the system and force them to recreate the temporary files.

Do NOT delete your database, just backup your files, delete them, re-upload them and youll be fine.

This is due to MySQL crash. Easily fixed and no data has been lost.

Sorry guys


Details:
MySQL crashed while writing data, it seems the temporary file has been corrupt and probably deleted by the system in an attempt to correct itself. This isnt a problem as the data is stored in a much more secure way to prevent this, and MySQL is coded to directly stop this. But as the file is now gone, the server cant write to it like it wants to because its not there, Error 13 is "Permission Denied". Now to fix it, Apache is already using our source files and a byte cacher is holding all our files and all has the old MySQL temporary file name, so you need to delete your current files, which will purge them from the cache, and then upload them again which will make fresh new entrys in the cache for the temporary storage. The temporary file is for holding data to be written to the database and its built like this so that this specific error cant happen to the database. This is highly unlikely to happen again, but then again it was highly unlikely to happen a first time.

~Trekkie

 

 

 


Comment/Reply (w/o sign-up)