Blog disabled by WordPress database errors

  • Resolved rastamad

    (@rastamad)


    18 years, 6 months ago

    Last week, I reported a problem with our blog not showing at all, and in lieu of it was an error message that says:

    It doesn’t look like you’ve installed WP yet. Try running install.php.

    It’s been a week and I haven’t gotten much help from WordPress support about the problem (For background, here’s the link to the topic I created last week). Our blog remains inaccessible as a result of WordPress database errors reported in the following:

    wp_comments
    wp_options
    wp_posts
    wp_users

    Our hosting provider tells us that the errors being reported in the MySQL database tables appear to be related to the WordPress script.

    Further, we were told that, since our WordPress blog is a third-party CGI script that we installed, they cannot offer support for third-party scripts and cannot troubleshoot the script for us.

    Instead, they suggested to restore the entire database. Or if what we would like restored is more detailed than that, to consult with WordPress about the “erring” script, as they need specific information before they can proceed.

    I do hope I get enough help and advice this time!

Viewing 15 replies - 1 through 15 (of 15 total)

  • Perhaps the database has become corrupted. If it is telling you that you need to install, it’s not detecting and users in the users table, which would be very odd for an existing blog.

    It’s been a week and I haven’t gotten much help from WordPress support about the problem

    Did you consider that your failure to respond to the original thread might effect the ‘help’ you receive?

    Your last post contained:
    While awaiting word from our host, I tried I logged on to PHPmyAdmin via our site’s control panel. I see there are a lot of MySQL errors in the following:

    What did your host say?

    What did your research reveal? Anything new?

    Have you considered deleting the db and starting over?

    Thread Starter rastamad

    (@rastamad)

    Sorry about that, Yosemite. I was preoccupied, frustrated even, dealing with our host about our problem. Basically, all they said in a span of one week were what I posted under this new topic, and the issue of a restoration fee, which they eventually agreed to waive if it happens to be a server-side issue.

    Here is one reply to my queries I haven’t posted:

    The errors indicate that the table structure was corrupted. Usually this is caused when a file was not properly written to the hard drive or saved correctly.

    But how is this possible when the upgrade to version 2.0.4 was successful, and we were blogging for two weeks since the upgrade? I haven’t encountered this problem with all other previous upgrades.

    My concern is that our host only allows us one database for our entire site, including the blog. Will restoring the entire database, instead of the affected tables in the database, not affect our site’s other content?

    Thread Starter rastamad

    (@rastamad)

    Our host has restored the MySQL database and the affected blog directories but the blog still doesn’t display and the following errors are shown instead. HELP PLEASE!

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘home’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘hack_file’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘active_plugins’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘permalink_structure’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘category_base’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘template’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘template’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘html_type’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘blog_charset’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘posts_per_page’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘what_to_show’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘gmt_offset’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘gmt_offset’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘gzipcompression’ LIMIT 1

    And when I go to wp-admin, I get this error page:

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘home’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘hack_file’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘active_plugins’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘permalink_structure’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘category_base’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘template’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘template’ LIMIT 1

    WordPress database error: [Got error 127 from table handler]
    SELECT option_value FROM wp_options WHERE option_name = ‘db_version’ LIMIT 1

    Your database is out-of-date. Please upgrade.

    Thread Starter rastamad

    (@rastamad)

    Our host says the WordPress version it uses is 2.0.2. It does not support the upgraded versions at the moment.

    Could this be causing the problems with the blog?

    Asked our host about the re-install, a downgrade to v 2.0.2. Tech support says it’s up to us.

    Would there be no problems if I downgraded to version 2.02? Would this solve the wp-options errors I mentioned above?

    Do you have access to phpMyAdmin? It has a repair option (where it will attempt to repair the db/tables)…

    Changing versions of WP will not have any effect.

    Thread Starter rastamad

    (@rastamad)

    I have access to phpMyAdmin but am no techie, not familiar how it works. Can you help me repair one by one the errors with the tables? (Remember they’ve just restored our database.) Our host would not do that for us, suggesting that we clear the tables WordPress uses and then do a reinstall.

    As with many PHP applications that rely on a database there may have been changes made to its tables as a result of the upgrade. Its also a very likely possibility it made some settings changes. However unless you know exactly how it looked before the upgrade it would be very hard to know what it did. I would suggest clearing the tables it uses and then reinstalling, see if that helps. Please keep in mind since you made changes by upgrading we cannot support your install, I am merely trying to offer some helpful suggestions.

    Will we not lose our archives of posts, comments, users, etc. since we started blogging in April last year?

    Will we not lose our archives of posts, comments, users, etc. since we started blogging in April last year?

    Yes, you will.

    This tutorial looks like it will do the job:
    https://paulstamatiou.com/2006/05/31/how-to-quickie-repair-mysql-tables-in-phpmyadmin/

    Note that whether wp_options has an overhead value or not, it should be selected for repair…

    Thread Starter rastamad

    (@rastamad)

    Thanks, Yosemite. I think it works. That tutorial was really useful. I’m adding it to my del.icio.us bookmarks. ??

    Thread Starter rastamad

    (@rastamad)

    Only you can’t really have everything. We lost posts between August 4 and August 12. ??

    Thanks again, Yosemite. You are our savior. ??

    Thread Starter rastamad

    (@rastamad)

    BTW, should I still downgrade to version 2.02. since it’s the version supported by our host?

    I experienced the same issue. I’ve read through the posts and will attempt to follow-up.

    As a bit more…I first experienced this issue on my blog on 8/18 after my provider automatically upgraded the WP release.

    After attempting to restore prior files based on prior server backups, I deleted the entire WP blog, and then established a brand new one based on the latest release, then painfully restored my content.

    Everything worked fine and I made a few additions. On 8/19, everything worked fine. On 8/20, I experienced the WP “Error establishing a databased connection.” That was the same issue first encountered on 8/18. This time I checked and SBC/AT&T showed my database as active. I have asked my provider for feedback on their side, but have not received a reply.

    Again, I’ll work through the prior posts, but I would like to find the root cause given the prior rebuild.

    BTW, should I still downgrade to version 2.02. since it’s the version supported by our host?

    I say no for 2 reasons:

    1) It is more insecure and buggy (2.0.2)

    2) Your host doesn’t give much support anyway ;’)

    Thread Starter rastamad

    (@rastamad)

    How about the posts that weren’t recovered? Are they lost forever? Tried Google cache but some are missing.

    Another thing, since I set up a temporary blog while our official blog was down, is ther a way of automatically transferring the posts (and comment) to the restored blog?

    If they are not in a backup somewhere (where you can retrieve it) then yes, it sounds like they’re gone. I think google cache was your only other chance.

    For the transfer question I suggest you mark this thread resolved and start a new one with that topic. This one is pretty ‘unwieldy’ (long) and the people who know more about recovery/transfer may be missing it.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Blog disabled by WordPress database errors’ is closed to new replies.