Automatic Update to WP 3.0.3 fails – couldn't resolve host wordpress.org

  • Tom Auger

    (@tomaugerdotcomyahooca)


    13 years, 4 months ago

    When I press the Automatic Update button to update to WP 3.0.3 I receive the following messages:
    Downloading update from http://wordpress.org/wordpress-3.0.3.zip…
    Download failed.: Couldn’t resolve host ‘wordpress.org’
    Installation Failed

    I have taken the following troubleshooting steps already:
    SSH to server and ping wordpress.org: OK

    ping downloads.wordpress.org: OK

    wget wordpress.org/wordpress-3.0.3.zip: FAIL – unable to resolve host address âwordpress.orgâ (what are those â??? )

    wget myotherdomain.com/downloads/somefile.zip: OK – wget works for other domains

    Installed Corecontrol and enabled HTTP Logging:
    GET http://api.wordpress.org/core/version-check/1.5/….etc : OK
    GET http://wordpress.org/wordpress-3.0.3.zip : ERROR (http_request_failed Couldn’t resolve host ‘wordpress.org’) timeout 300 HTTP Transports WP_Http_Curl

    —-

    I’ve seen a number of posts suggesting to change the curl timeout value. But here the request is NOT timing out – it can’t resolve wordpress.org host.

    And yet I can ping wordpress.org from the server, and I can type wordpress.org into my browser window (on the server). So what gives?

    Need help desperately. Can’t install plugins from the control panel either.

    Thanks

Viewing 15 replies - 1 through 15 (of 15 total)
  • Moderator t-p

    (@t-p)

    13 years, 4 months ago

    try manual update.

    http://codex.wordpress.org/Updating_WordPress

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    Haha. Thanks. Funny guy.

    No, I need to get the automatic update feature working as well as download/install of plugins through the admin CP.

    Anyone else with a solution or direction my troubleshooting should go?

    Thanks

    Moderator t-p

    (@t-p)

    13 years, 4 months ago

    -The reason I suggested manual upgrade was in case the autoupgrade had issues.

    -also I would suggest contacting your hosting provider and discussing the issue with them.

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    Thanks for this clarification.

    If auto-upgrade in 3.0.1 has documented issues with bug tickets reported, then I would like to hear about it. But I strongly suspect the issue is on my end.

    Also, I am the hosting provider – it’s running on my server. Based on the technical details in my original post, I’m expecting the problem to be with my server configuration, and that’s the kind of advice I’m hoping someone will post in reply to my question.

    Cheers

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    13 years, 4 months ago

    Try restarting Apache.

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    Appreciate the thought. $sudo service httpd restart has no substantive effect the last time I tried it. Any other ideas?

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    13 years, 4 months ago

    Well, looking around Google, I see that this is a problem often encountered with curl, but I can’t find any resolution for it.

    Some people stated that if they run their apache as root, it works, which indicates some form of permissions problem with regards to the user the webserver is running as and DNS capabilities.

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    Thanks for the follow-up post Otto. I would be tempted to agree with the curl assessment except that $wget wordpress.org/wordpress-3.0.3.zip doesn’t work either – unable to resolve the host address. Unless wget uses curl or vice versa, I’d say the problem lies elsewhere.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    13 years, 4 months ago

    Not necessarily. It’s a system level thing. Both curl and wget use the same backend libraries to do DNS resolution. Perhaps you’re just getting local cache failure or something?

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    I”m not sure I understand what local cache failure means, but it sounds plausible. A very strange thing happened this morning: I did a wget from downloads.wordpress.org/… (through a telnet connection on my server) and for the first time it worked! Then I went into WP Admin and tried the auto-update. It took a long time and then failed, just like before.

    Here’s the strange part:
    I then telnetted in back to the server and did the very same wget on downloads.wordpress.org and it FAILED! It had just succeeded, and then after trying auto-update, the same request failed with “Temporary failure to resolve host”.

    So in fact the auto-update somehow “broke” the DNS lookup. How is this possible?

    T

    Mark Ratledge

    (@songdogtech)

    13 years, 4 months ago

    So in fact the auto-update somehow “broke” the DNS lookup

    Autoupdate isn’t going to break DNS because it can’t change DNS. Ask your host; they have something funky with DNS or local caching as Otto pointed out or restrictions in curl.

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    I am my host. I asked myself, but I was being truculent and wouldn’t answer. In fact I suspect I just don’t know the answer. Multiple personalities suck.

    Seriously, I need guidance because I’m on my own here. Any further help anyone can offer will be greatly appreciated.

    Tom

    Mark Ratledge

    (@songdogtech)

    13 years, 4 months ago

    Time to look into server admin and DNS. Server Fault is a good place: http://serverfault.com/

    Thread Starter Tom Auger

    (@tomaugerdotcomyahooca)

    13 years, 4 months ago

    way ahead of ya songdogtech. Well, not way ahead of ya. Ahead by 2 hours 🙂

    Thanks for the thought. I’m starting to feel like these forums are not the greatest place to get technical advice.

    Mark Ratledge

    (@songdogtech)

    13 years, 4 months ago

    They are for WordPress; not necessarily for topics like server admin.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Automatic Update to WP 3.0.3 fails – couldn't resolve host wordpress.org’ is closed to new replies.

Tags