I'm not sure how long these have been happening but noticed in the log... intermittend errors like this one:
Got error -1 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 LEFT JOIN forum_access fa ON t.tid = fa.tid LEFT JOIN acl acl_fa ON acl_fa.name = t.tid AND acl_fa.module = 'forum_access' LEFT JOIN acl_user aclu_fa ON aclu_fa.acl_id = acl_fa.acl_id AND aclu_fa.uid = 0 WHERE ((fa.grant_view >= 1 AND fa.rid IN (1)) OR fa.tid IS NULL OR aclu_fa.uid = 0) AND ( r.vid = 7539 )ORDER BY v.weight, t.weight, t.name in /home/folder/public_html/modules/taxonomy/taxonomy.module on line 617.
Any ideas what might be doing this? Haven't been able to find any pattern to it yet (though there was a similar error occuring whenever I ran Rebuild Permissions... until I uninstalled Taxonomy Manager. But these seemingly random errors have continued.

Comments

salvis’s picture

salvis
he/his
commented

No, I have no idea, sorry.

Try reformatting the query and wrapping lines so that you can actually figure out what it does.

Then try running it through phpMyAdmin and see whether you get the same error.

aharown07’s picture

aharown07 commented

I think this may be fixed now. No error -1 or incorrect key file or error 28 since sometime yesterday afternoon.

As I was looking around in the sites/all/modules folder, found a curious folder named "ites"... contained /all/modules/scheduler and a couple of other folders.
Put these modules where they belong and reinstalled them.

I believe I know how this happened: sometimes when unpacking tar.gz files using the cPanel File Manager, the unpack-to field fills with a partial string... the result is that unpack operation recreates the folders in a new dir instead of unpacking them in the current one. I've seen this multiple times and usually catch it right away, but it's a gotcha. Don't know why the FM behaves this way. (I use FF if that matters)

Anyway, fixed the folder goofiness and it looks like maybe no more errors. Will watch for a while.

salvis’s picture

salvis
he/his
commented
Status: Active » Fixed

Ok, thanks for letting us know.

Yes, Drupal hates it when duplicate module files are hanging around.

aharown07’s picture

aharown07 commented

I can confirm that fixing the directory structure in sites/all/modules ended this error. In this case, I didn't have duplicate module files, but two modules were basically running from sites/all/modules/ites/all/modules/modfolder

Sort of amazing they worked at all.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

gennadiy’s picture

gennadiy commented

in my case it was low free disk space on the system drive