By Dan01 on

Our webhosting company upgraded over the weekend, and today we are getting an error message that shows up when we add a story, delete a node, publish a node, accessing the logs, and when accessing the taxonomy.

Currently the host is running :
Apache version 2.2.9 (Unix)
PHP version 5.2.6
MySQL version 5.0.67-community-
log

It seems like it is sporadic as it does not happen every single time.

Haven't upgraded to 5.0 because of theming issues. Running the 4.7.11 drupal install.

Has anyone else had this problem?

Is there an easy fix?

Here it the error message. It looks like we don't have write permissions or access to the .myi file, but the host says that is not the case.

Incorrect key file for table '/ramdisk/mysql/tmp/#sql_****_*.MYI'; try to repair it query: SELECT DISTINCT(n.nid), n.title, r.body, sticky, created FROM term_node t INNER JOIN node n ON t.nid = n.nid INNER JOIN node_revisions r ON r.vid = n.vid INNER JOIN node_access na ON na.nid = n.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all') OR (na.gid = 1 AND na.realm = 'term_access'))) AND ( t.tid IN (2,3,1,7,4,8,6,56) AND n.status = 1 ) ORDER BY sticky DESC, created DESC LIMIT 6 in /includes/database.mysql.inc on line 121

⋅ Categories: Drupal 4.7.x

Comments

Dan01’s picture

Dan01 commented

I actually think I am running the 4.7.10 install, I am going to update to the 4.7.11 and see what happens.

Dan01’s picture

Dan01 commented

It didn't fix the problem.

Dan01’s picture

Dan01 commented

The problem looks like it is related to mysql. It has to do with the size of the tmp file

It looks like it is an issue that happens from time to time. See URL below:

http://forums.mysql.com/read.php?21,18281,180813#msg-180813

Dan01’s picture

Dan01 commented

Guess what. I checked another install on another one of our websites that has drupal 6 installed and it also has the same error message. They said they upgraded the mysql here as well.

The hosting company is refusing to fix the size of the tmp because it is related to memory size... So I am dead in the water unless, there is something I can tell the web host to do that with a patch or something from mysql. The websites work, but the error message seems like it could possibly corrupt data.. I am not certain that this would happen or not.

Anybody else having this problem?

Dan01’s picture

Dan01 commented

web host company said that they realized that the defaults were put back after they did the update to mysql and they will put back the original settings. So I think the problem should be resolving soon.

One idea they did offer was to create a composite index for one database to work around a memory hog problem. I am not sure if there is a module that is available to do this but it sounds like a good idea.

I want to work on getting the database split off into seperate units and have one front end access multiple databases. I would think this would help my resource problem that I have because my database and users keeping growing year after year. But, that is another issue.