Forums

2.3 upgrade fails to complete (3 posts)

  1. RaphK
    Member
    Posted 4 years ago #

    The automatic Fantastico upgrade and the upgrade.php upgrade within WordPress itself are both failing to complete.

    In both cases, I can access the blog itself just fine but cannot get to the admin dashboard. I am told that I need to upgrade my database. When I click the link, I just get a blank page with the WordPress logo. When I try via Fantastico, I get as far as "backup created" and no further messages.

    When this happened, i resorted to a manual upgrade. All files are at the 2.3 release, and the page source reports 2.3 as well. All plugins are disabled too. But the same thing still happens.

    Is there are way to tell where it is failing? I do have a backup of the database.

    Examining the current database after the failed upgrade shows that wp_terms, wp_term_relationships and wp_term_taxonomy were in fact created, but they are empty.

    The database has around 20k comments, and 2k posts going back to 1998. I saw one thread that suggested this might be PHP timing out?

  2. RaphK
    Member
    Posted 4 years ago #

    A friend suggested forcing a database upgrade:

    http://codex.wordpress.org/FAQ_Installation#How_do_you_force_a_database_upgrade.3F

    ...which I didn't see the point of, given that said upgrade is exactly what was failing each time. But it did make me go look at the value of the db_version field in the wp_options table. Which was "1" instead of what it should be.

    I changed it manually to 4773, and the upgrade link succeeded, and now it's at 5183 (which is correct since we are currently running 2.2.3).

    I will now try going to 2.3.3, and won't mark this resolved until it makes it all the way there. :)

  3. RaphK
    Member
    Posted 4 years ago #

    Turns out that all this (and more -- blank line in RSS feed, zillions of rss_gibberish keys in the wp_options table, spam inserted into footer and header and index.php) was all because of the goro injection attack or the wordpress.net.in injection attack.

    After many hassles, I am up and running at version 2.5.

Topic Closed

This topic has been closed to new replies.

About this Topic