My websites (Drupal 5.6) often has the following message. This is only appear occasionally and only display to some pages with taxmony terms. Anyone got the same problem? Actually, it also appears on my D6 sites. Is it the problem of my server?

-----------------------
user warning: Got error 28 from storage engine query: SELECT DISTINCT(p.perm) FROM role r INNER JOIN permission p ON p.rid = r.rid WHERE r.rid IN (1) in /home/ibcacth/public_html/en/includes/database.mysql.inc on line 172.
user warning: Got error 28 from storage engine query: SELECT t.* FROM term_node r INNER JOIN term_data t ON r.tid = t.tid INNER JOIN vocabulary v ON t.vid = v.vid WHERE (t.tid IN ('1','2','3','5','6','8','9','10','11','14','15','16','17')) AND ( r.nid = 92 ) ORDER BY v.weight, t.weight, t.name in /home/ibcacth/public_html/en/includes/database.mysql.inc on line 172.
user warning: Got error 28 from storage engine query: SELECT DISTINCT b.* FROM blocks b LEFT JOIN blocks_roles r ON b.module = r.module AND b.delta = r.delta WHERE b.theme = 'ibc_faqing' AND b.status = 1 AND (r.rid IN (1) OR r.rid IS NULL) ORDER BY b.region, b.weight, b.module in /home/ibcacth/public_html/en/includes/database.mysql.inc on line 172.

Comments

faqing’s picture

After I logged in, the message disappears. I just don't understand this problem.

nmridul’s picture

I'm also getting a similar error...

"user warning: Got error 28 from storage engine query: SELECT t.* FROM term_node r INNER JOIN term_data t ON r.tid = t.tid INNER JOIN vocabulary v ON t.vid = v.vid WHERE r.vid = 8 ORDER BY v.weight, t.weight, t.name in /home/mridulna/domains/mridul.co.in/public_html/modules/taxonomy/taxonomy.module on line 618".

faqing’s picture

I solved my problem by increasing the PHP memory, see here how: http://thanhsiang.org/faqing/node/95

bomarmonk’s picture

The php memory increase above worked for the time being! Excellent!

ttripp’s picture

Just woke up to this error on one of my smaller sites. First tried emptying the /tmp folder to no avail. Noticed that while I was getting the error I couldn't even optimize tables having overhead or empty tables like cache...
Finally tried the .htaccess mod to increase PHP memory and it worked. Thanks for the tip!!!!

betawavetom’s picture

I am receiving the same issue.
Hostgator is being helpful in trying to resolve this, but we are not finding where the true culprit lies.

Anonymous visitors get the error and consequently an "access denied" page, whilst when I log on everything is fine.
Website in question is http://www.breastfeedingconferences.com

-
I do not see things the way they are - I see them the way I am

MGParisi’s picture

Host Gattor limits PHP Memory to 64Mbits. This will greatly limit your success in Drupal and maybe why no changes to php memory in php.ini fixes the issue.

betawavetom’s picture

I am receiving the same issue.
Hostgator is being helpful in trying to resolve this, but we are not finding where the true culprit lies.

Anonymous visitors get the error and consequently an "access denied" page, whilst when I log on everything is fine.
Website in question is http://www.breastfeedingconferences.com

--
Actually, it is ALL Drupal websites [version 5.x + 6.x] that are affected.

-
I do not see things the way they are - I see them the way I am

Fixdit’s picture

So what was the cause of this issue and the fix, I'm experiencing the same problem!?!?

MGParisi’s picture

It could be that you are running out of Memory.

Or

You can delete all files under /tmp (this is not under publc_html) but in the same directory this folder is.

I indiscriminately deleted everything under the /tmp directory and it fixed the issue. I do not know why this would be a problem, I have plenty of space according to Cpanel. I have a feeling the tmp directory has its own limits on how much space it can consume.

faqing’s picture

The tmp file directory for mysql caused the problem. You can check your cpanel server status.

Cyberespia’s picture

I am receiving the same issue, my site www.adictoshp.org with drupal 6.12
helpp

keesje’s picture

Disk size (lack off, to be specific) is the culprit indeed. In my case this message was logged mostly during nightly hours.
The cause was temporary diskspace usage by the nightly backup script, archiving all user data on the server daily consuming all diskspace available. So, cleaning up your /tmp folder might help, but does not solve the issue itself in most cases. A webserver admin has to make sure there is plenty of extra room (>25%?) on the harddisk for temporary files and backups. This issue is not Drupal specific.

Luck,

Kees