PageSearchIndex is marked as crashed. Help!
Permalink
I was on my client's site to make a simple change and the first thing I went to do was click on the Sitemap in the dashboard. I got a "Database error occured while processing this request". I then checked the logs and found a number of errors saying "Table PageSearchIndex is marked as crashed and should be repaired".
In another related thread, the submitter was instructed to run REPAIR TABLE PageSearchIndex through mysql. It fixed the problem for them, but I'm worried that this could make things worse.
Everything else in the site seems to work; at least I can view all pages and edit them. I haven't tried to add a page.
Note that this is not an upgrade. Site is been running fine since May on 5.3.3.1.
The site is using google search so I'm wondering if this table is mainly for c5 searching? Does anyone know if "REPAIR TABLE" is safe? I'd appreciate any advice on this. Thanks.
In another related thread, the submitter was instructed to run REPAIR TABLE PageSearchIndex through mysql. It fixed the problem for them, but I'm worried that this could make things worse.
Everything else in the site seems to work; at least I can view all pages and edit them. I haven't tried to add a page.
Note that this is not an upgrade. Site is been running fine since May on 5.3.3.1.
The site is using google search so I'm wondering if this table is mainly for c5 searching? Does anyone know if "REPAIR TABLE" is safe? I'd appreciate any advice on this. Thanks.
well you could always just make a backup and then do it... couldn't get any worse.
I'm just wondering if I do a repair and data is lost, does it really matter with this table? The client is not using the c5 searching capability anyway. I just don't get why the sitemap would be trying to use this table. I tried looking through the code and it seems to be only used for search indexing from what I can tell. Is there anyone who knows how this table is used?
Thanks.
Thanks.
no, Im pretty sure this isn't for c5 search but for the page listing index. try do into the dashboard, system/maintenance, and then run the search index job.
According to MySQL docs, this error means there is database corruption so I don't think re-running the search index job will even work. It will probably receive the same error from MySQL. Unfortunately, this error is in their logs from 2 months ago and they have made lots of changes since then, so I probably can't go back to an old backup. Arrrrg...
just repair the table, (its a mysql function)
I will go ahead and do that. I also did a test on my own machine with a local copy of the DB and emptied out that table and everything on the site worked so now I feel much better. I then ran the job to generate the search index and it filled up so I am pretty sure that is all it is used for (although it does break the sitemap -- maybe because the sitemap has a page search tab?).
Thanks for your help.
Thanks for your help.
