This is a second part:
WordPress database error: [Got error 127 from storage engine]
SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND post_date_gmt <= ‘2006-05-12 01:08:59’ AND (post_status = “publish” OR post_author = 1 AND post_status != ‘draft’ AND post_status != ‘static’) AND post_status != “attachment” GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 0, 50
Googling the 127 error for MySQL shows that’s it’s one of those “unexpected problems” and it appears that it’s likely to go away. Does every query afterwards produce the same error? If so, the database may be corrupt and you should read this:
http://www.databasejournal.com/features/mysql/article.php/3300511
The problem arose in connection with the failure of a Comment of mine to upload.
I can backup from saved earlier versions.
Can you tell me what file the comments would be found in? Presumably, the Directory is “Content.”
The comments are in the database table comments (prefixed with whatever prefix you chose at install time). If by “file” you mean what is the name of the script which updates comments, that’s kept in your theme directory: /wp-content/themes/yourthemename
My question was which file would I replace using an earlier backup edition to correct the corrupted Comments database table.
Unfortunately, I using Yahoo for my domain host. SQL has a repair tool, but I don’t get to use it. I just get to submit a reqest for a database repair, and who knows when they’ll do it.
Thanks for the help.
It’s very likely that your entire database is in the one file. It depends on how (and with what) the backup was made. Usually, backups go into some “.sql” file, which is just text. The normal and safest way to restore is to restore your entire database, not just one table. If that’s what you’re going to do, it should be simple enough by loading the backup “.sql” file into some sort of database client software (I don’t know what you use, I just use good-old SSH) and restoring everything to some point in the past.
Restoring just comments may work but you’re going to have to remove all the other references to other tables in the “.sql” file. In any case, you may end up with integrity problems doing this.
Update. It’s fixed.
I got no help from Yahoo hosting, over 36 hours.
I got into the blog to the Write page, and wrote and uploaded a test message. Causng the software to cycle, and upload, fixed the SQL database.
I’m shaking my head at how easy it was to fix. But who knew? I also thought a possible result was an even more screwed up database, before I tried it.
I just experienced this same error. I’m with yahoo hosting. I was able to login to my phpMyAdmin and create a backup.
After that point all was back to normal. I didn’t even have to repair/restore or anything like that.
I’m just happy I didn’t have to deal yahoo !support.
11 days later this happened once again. I went into phpMyAdmin. Repaired wp-posts table.
That table was the problem because phpMyAdmin reported back things like:
“Found block that points outside data file at 56297…”
And then at the end it said:
“warning: Number of rows changed from 1136 to 1133” (i’m guessing i lost 3 posts here )
Any idea how I can find the lost posts?
But anyhow, database was fixed at the end.
I use Yahoo’s “backup database” request at least once a week.
Perhaps you can find the lost postings via a cache from a Google search.
