3.1.1 Network Update Fails — Empty Response From Server

  • Resolved jchook

    (@jchook)


    15 years, 2 months ago

    Running WordPress 3.1, updating to 3.1.1

    Using WPMU Dev Multi-DB plugin, which utilizes sunrise. However, disabled ALL plugins and mu-plugins except for Multi-DB before updating.

    Manually downloaded and installed files for 3.1.1. WordPress says update was success; now I just need to update network. This has worked fine in the past, including the recent update to 3.1.

    I click update network, but the first site fails.

    WordPress says:
    Warning! Problem updating http://username.example.com. Your server may not be able to connect to sites running on it. Error message: 0: Empty reply from server

    PHP says (via DEBUG_MODE):
    Warning: http_request(): server returned nothing (no headers, no data); Empty reply from server (http://username.example.com/wp-admin/upgrade.php?step=upgrade_db) in /wordpress/www/wp-includes/class-http.php on line 1236

    What seems weird to me is the lack of response, especially with DEBUG_MODE enabled. The same request run from wget on the local environment returns a handful of PHP Notices, and there should at least be some headers.

    Any ideas?

Viewing 15 replies - 1 through 15 (of 18 total)
1 2
  • Thread Starter jchook

    (@jchook)

    15 years, 2 months ago

    Also having another issue… the maintenance_mode option for the main blog (no special subdomains) was set to 1 after my initial upgrade attempt. what is going on?!

    This is a x.x.1 update and it’s giving me infinitely more headaches than the updates to 3.0 or 3.1.

    Also, just a couple more details…

    1. I was able to visit username.example.com and it worked fine, despite failing the network update
    2. I tried updating with mu-plugins enabled. Same result

    Thanks in advance for any help!

    Andrea Rennick

    (@andrea_r)

    15 years, 2 months ago

    Using WPMU Dev Multi-DB plugin,

    paid plugin, go ask them. likely it needs updating.

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    I am also having this problem, but am not using the wpmu dev multi-db plugin. only plugins installed are askimet and nextgen-gallery, but both are disabled. i am able to visit all blogs, but when i try to update network, i get the same message jchook was(/is?) getting.

    Tim Moore

    (@tmoorewp)

    15 years, 1 month ago

    You can visit the specific blog that the error message is talking about? Can you get to its Dashboard?

    Andrea Rennick

    (@andrea_r)

    15 years, 1 month ago

    Have you actually got any sub sites?

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    Yes I have quite a few sub sites.

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    And yes, I can visit the specific blog that the error happens on. The error happens on the very first blog, so I have no sites updating correctly.

    Andrea Rennick

    (@andrea_r)

    15 years, 1 month ago

    force update blogs to continue
    /ms-upgrade-network.php?action=upgrade&n=80 <— change last number

    Thread Starter jchook

    (@jchook)

    15 years, 1 month ago

    Andrea_r, thanks for suggestion.

    I am still unable to upgrade, no matter what value I use for n. Every sub-site fails to update.

    paulwoolcock, so glad you are having the same problem and not using multi-db haha. Can you check your PHP error logs to see if there is any output from the update script?

    Seems the network update script is attempting to create tables that already exist or something. Here is my WordPress PHP log output when I attempt to update:

    [Code moderated as per the Forum Rules. Please use the pastebin]

    Andrea Rennick

    (@andrea_r)

    15 years, 1 month ago

    @jchook – have you talked to the multi db plugin devs yet?

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    @andrea_r I am assuming the n=80 should be changed to n=<number of subsites> ?

    Andrea Rennick

    (@andrea_r)

    15 years, 1 month ago

    No, the n=80 is the blog id of the next blog to start at. When working normally, on each page refresh that number increases or decreases by 5.

    (I can never remember what order it goes in.. up or down)

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    no matter what blog i start from, I get the same error message: Your server may not be able to connect to sites running on it. Error message: couldn't connect to host

    Tim Moore

    (@tmoorewp)

    15 years, 1 month ago

    Paul, do you have a special server set up of any kind? Are you using a development server or a custom hosts file?

    paulwoolcock

    (@paulwoolcock)

    15 years, 1 month ago

    nope, standard LAMP server with standard config.

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

The topic ‘3.1.1 Network Update Fails — Empty Response From Server’ is closed to new replies.