Hello,

I have mysql error

user warning: Got error 134 from storage engine query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '3:efb618d90a023f18f010efb25d80840b' in /var/www/vhosts/website.com/httpdocs/includes/database.mysql.inc on line 174.
user warning: Got error 134 from storage engine query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '3:0fd70206742dc6a7d79acb2eb8a5cdfe' in /var/www/vhosts/website.com/httpdocs/includes/database.mysql.inc on line 174.
user warning: Got error 134 from storage engine query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '3:1fe422f043a013a4988e97abbf0bd4dc' in /var/www/vhosts/website.com/httpdocs/includes/database.mysql.inc on line 174.
user warning: Got error 134 from storage engine query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '3:a7bcdfb229fe8e87151ea795f58ba2ab' in /var/www/vhosts/website.com/httpdocs/includes/database.mysql.inc on line 174.
user warning: Got error 134 from storage engine query: SELECT data, created, headers, expire FROM cache_filter WHERE cid = '3:b88bc695695d460cdadc799854a06840' in /var/www/vhosts/website.com/httpdocs/includes/database.mysql.inc on line 174.

I tried to repair cache_filter table, but doesn't work.

Any help?

edited by silverwing - changed forum

Comments

pbarnett’s picture

cache_filter, like all the cache_xxx tables, can be emptied (but not dropped!) safely. Try that.

arrisweb’s picture

arggh I dropped by mistake :(
I have tar backup. Do you know where is database located in tar?
I want to get this table from backup.

Thanks

arrisweb’s picture

Ok.

I find out how to create that table.

CREATE TABLE cache_filter (
cid varchar(255) NOT NULL default '',
data longblob,
expire int NOT NULL default '0',
created int NOT NULL default '0',
headers text,
PRIMARY KEY (cid),
INDEX expire (expire)
)

works fine, but only 5 errors like before.....

arrisweb’s picture

No it's empty, but still the same errors. I don't get it :(

pbarnett’s picture

Probably best to empty all the cache_xxx tables.

Easiest way to do this is to install the admin menu module, which makes clearing all or selected caches simple - http://drupal.org/project/admin_menu

arrisweb’s picture

Thanks I will try it

arrisweb’s picture

I emptied cache_menu and cache_content and it is works great.

Thank you again :)

pbarnett’s picture

You're welcome; I'm pleased that you have got it working again!