wp-admin returning 500 errors after update to 4.2.1

  • Site owner updated her multisite yesterday via the dashboard. The site itself is still running, but the network and primary site dashboard both return a 500 error. However, the wp-admin for two subdomain sites can be accessed just fine.

    The related PHP errors showing up are these:

    [Mon Apr 27 23:36:21 2015] [warn] [client x.x.x.x] mod_fcgid: read data timeout in 45 seconds
[Mon Apr 27 23:36:21 2015] [error] [client x.x.x.x] Premature end of script headers: update-core.php

    I’ve tried disabling all plugins and changing theme to twentyfifteen, but the issue persisted. Anyone seen this or have any ideas?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter John Chandler

    (@euangel)

    An update: I rolled the site back to 4.1.4 and everything was working fine again. I tried the upgrade again to 4.2.1 and lost access again.

    The seems to be network issues between your server and www.remarpro.com. You might want to consider upgrading manually.

    Thread Starter John Chandler

    (@euangel)

    That had been my first thought too, but I tried to manually delete and upload the core files and that wasn’t a fix.

    My client also has this problem since they updated to 4.2.1. PHP version is 5.3.

    Could this be that plug-ins need to be updated as well? But how do you do that when you can’t log into WordPress?

    Update:

    We solved this issue by upgrading PHP to 5.4.40.

    Thread Starter John Chandler

    (@euangel)

    I was also running PHP 5.3, and just completed the upgrade to 5.4.40. Unfortunately, once I updated the site to 4.2.1, it’s still throwing back the same 500 error.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    [Mon Apr 27 23:36:21 2015] [error] [client x.x.x.x] Premature end of script headers: update-core.php

    How big is your database?

    That end of script makes me think your DB is timing out on the utf8mb update.

    Thread Starter John Chandler

    (@euangel)

    Mike — Thanks that actually seems like the most viable explanation I’ve seen. The total database is 4.8gb.

    Any tricks to help get it through that DB update?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Holy noodles! ??

    Uh. You don’t have WP-cli installed, do you? Otherwise you kind of have to keep running until it finishes.

    Thread Starter John Chandler

    (@euangel)

    I do have wp-cli installed. (I do now, anyway!)

    Comment tables are huge due to spam, so trying to trim those down, but I assume you ask because wp-cli also be used to update the tables for the update?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Yes!

    wp core update-db

    https://wp-cli.org/commands/core/update-db/

    Keep rerunning it until it’s done.

    Thread Starter John Chandler

    (@euangel)

    Thanks.

    I ended up clearing out thousands and thousands of spam comments via mysql queries and then the upgrade ran like a dream.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘wp-admin returning 500 errors after update to 4.2.1’ is closed to new replies.