Anonymous
Unregistered
Posted 8 years ago #
Hi,
I have just got WordPress running, but when I browsed to index.php using my browser, the following error message appeared on the right hand column :
QL/DB Error:
[Can't create/write to file '/tmp/#sql_111_0.MYI' (Errcode: 28)]
SELECT DISTINCT link_category, cat_name, show_images, show_description, show_rating, show_updated, sort_order, sort_desc, list_limit FROM wp_links LEFT JOIN wp_linkcategories ON (link_category = cat_id) WHERE link_visible = 'Y' ORDER BY cat_name
Can anyone direct me to the relevant files so that I can manually edit the path of the temp file to some where with the correct permissions?
Thanks a lot!
That is a MySQL error, you might want to try searching MySQL forums or documentation for better guidance. It sounds like it's having trouble creating temporary tables.
macangel
Member
Posted 8 years ago #
I had that problem and it was a file that the server admin had to deal with. Write t your web host and tell them about it. They should be able to correct it for you. It is related to other sites on the save server filling up the tmp file.
Anonymous
Unregistered
Posted 7 years ago #
My host disabled my account because I was supposedly creating wierd files in the /TMP directory. Is this caused by wordpress?
Very unlikely that is caused by WP. The number of total wordpress blogs is (was?) 24219 and increasing...
http://wordpress.org/support/7/13002
and they do not report "weird" files. Try to work out with your host what was the problem.
frankmarion
Member
Posted 6 years ago #
What this is telling you is that mysql is pointing to a folder that is non-existent, or that does not have the permissions to write to. The problem is not with WordPress, but with MySQL's .ini pointing to the an inacessible location. See the MySQL documentation as a pointer.
http://dev.mysql.com/doc/mysql/en/temporary-files.html
zzzmarcus
Member
Posted 6 years ago #
I'm having a similar problem--if /tmp isn't executable, WordPress won't run (many other php/mysql scripts will).
Is there some way to keep /tmp from being executable and still have WordPress work?