Hi every one,

Since the last Drupal upgrade (6.12 to 6.13) he can't find any update information. the error message is "Unable to fetch any information about available new releases and updates" and nothing else.

My hoster confirm that port 80 was open (I reconfirm with a nmap) and they don't change anything at server configuration. They told me that I'm not the first one who's contact support for this problem.

I'm trying to launch a update.php with contributed module activate and deactivate but nothing is changed.

I never had any problem before the last Drupal upgrade.

Have any one a idea ???

Thank you in advance...

Comments

dbeall’s picture

I have a site doing the same thing, but it was upgraded when 6.13 was released on July 1st.
It is not the upgrade doing it here, in fact the upgrade when I did it went just fine.
All of a sudden the update page shows empty with same error, click operations in the database log box does nothing.
I guess I don't need to know if it's up to date as long as I have a backup when it goes down.

cdpapoulias’s picture

Just confirming that I'm seeing the same error on my installation of Drupal with 6.13.

pepemty’s picture

Same thing here in a new install.

Pepe

Warm regards from sunny México!
Pepe
:-)

Yannick WEBER’s picture

I think I'm waiting a week and I'm going to make a bug report...

I've find a provisional solution :

  • Launch a update.php
  • Put your site in maintenance
  • Select the last Drupal's update module version (6000 for me)
  • Clic on "Update" to execute it

    It's done

    I don't no if it's working on all 6.13 installation because it's only working for one of my Drupal sites.

  • pepemty’s picture

    But it didn't work for me. :-(

    Warm regards from (way too) sunny México!

    :-)
    José

    Warm regards from sunny México!
    Pepe
    :-)

    ponsich’s picture

    Hello

    I have the same problem, and it didn't work for me too. :-(

    ponsich’s picture

    My problem is solved by itself.
    I do not understand what happened!

    pepemty’s picture

    After the ImageCache module had a security upgrade, Update Status worked again.

    Pepe

    Warm regards from sunny México!
    Pepe
    :-)

    molvar’s picture

    I am having the same problem. I have been unable to check for updates for at least 4 days now. I run cron, check manually, and still get the message "unable to fetch...". I have been running 6.13 ever since it was first released but this is just now occurring.

    cdpapoulias’s picture

    The install I'm referring to above is a Mosso (Rackspace Cloud) install that I've had no problems with until a little while ago. I just spoke with their tech support and they're not 100% sure yet if its a Mosso problem or a problem in the code. They have not disabled outbound port 80, which I know Drupal uses.

    They say its a problem with the script being able to resolve drupal.org for some odd reason.

    I'll try to keep this updated.

    -D

    dbeall’s picture

    I knew one of the modules was at fault in my case, but never found it till today, Imagecache was causing it. The module had a security upgrade today, and the available updates came right back after running update.php.
    D6.13 since release, all modules are the newest dev version other than one poll mod.

    iharley’s picture

    I'm having the same problem with two different sites (same server). One has Imagecache, and the other doesn't. I'm not running a multi-site setup.

    dbeall’s picture

    I was reading where disabling and/or uninstall modules to find the one causing issue works, but with lots of modules this is a task. Maybe check to see which ones were added or upgraded recently and start with those.

    iharley’s picture

    After enabling and disabling a large number of modules I had still not found the problem. I finally decided to try my host, though they've been less than helpful in the past. Turns out they had blocked my sites from communicating with Drupal. All's well now.

    Macronomicus’s picture

    Same problem here ... and its strange as it only just started happening .. I upgraded to 6.13 a while ago and have done many updates since then. This also ruins Drush update because it relies on the update module.

    Still havnt figured out what the problem is .. but since we are all getting this I think its highly unlikely to be a server problem, were all on different systems and getting the same problem. ahhh damn ..

    My test servers update seems to not work at all, and my production server will check updates but when running drush update commands nothing happens, no updates are downloaded or made.

    Macronomicus’s picture

    Ok well it is working on my live server . nevermind that! Just not on my test server like I said above.

    Macronomicus’s picture

    It was apparmor on my ubuntu test server there was a named profile which was mucking things up .. on my live server there is not a named profile probably because on my test server I use wildcard dns to create fake domains and this profile was likely auto created.

    Man that was a pain in the but! All is working as expected now.

    EDIT: Here is the link to the bug/problem & solution in case someone else is getting the same thing. Its not drupal related but it breaks drupal updates.
    http://ubuntuforums.org/archive/index.php/t-735188.html

    emdalton’s picture

    The update goes into an infinite loop. When I gave up and restarted it, I realized that I couldn't select any specific versions on the update screen. In my log, I see:

    "Attempted to fetch information about all available new releases and updates."

    This never returns successfully. I pulled out the two modules I had updated today, but no luck.

    bramface’s picture

    This began happening at the same time with two multi-site installations, two different versions of Drupal. So, very hard to believe it's just one module.

    The first time I ran this, I noticed that some of the modules showed update data and others did not.

    It seems very clearly to be a timeout issue, and one would presume the timeouts were being caused by modules in sequence - e.g. my Drupal 6.13 was reported as Up To Date, my admin_menu was "Failed to fetch available data", and then three more modules reported up-to-date, and then the "faileds" continued for the rest of the set.

    So, my guess was that if it had anything to do with a module at this point (which I find hard to believe, because of that first thing I wrote), it would be "admin_menu". I removed and re-installed the latest stable version. Then "checked manually" again.

    This time, it made it a little further. The module that got "stuck" was color_soc08, and this was a dev version, so I deleted it.
    Ran manually again, got hung up at "image" which went from Alpha to Beta. Installed the Beta, ran Update.php...and now things were worse than before. Hung at cck 5 -2.5, which is stable.

    So much for that theory, then. I'm voting for a server timeout. Is the timeout being caused by an infinite loop? If so, it is not Drupal-related, since this happened with both 5.x and 6.x sites at the same time (with far more profound impacts for the 5.x sites - I had to disable update_status to keep them going).

    Speaking for everyone else on this thread, if we can't solve this soon, we're going to have big problems keeping our sites updated. Maybe it's time to use Drush for that purpose.

    --
    Bram Moreinis
    Greenfield Digital
    http://greenfielddigital.com

    Pilot’s picture

    Just a note - I had (have) the same problem on a relatively clean drupal 6.13. I tried uninstalling modules to no avail. Anyhow, without laying out specifics (though happy to share if anyone decides to get really serious about tracking the source), I seem to have resolved the problem by upping the time limits in my php.ini. In my Apache2/php.ini changed the following:

    post_max_size = 32M

    mysql.connect_timeout = 120 ;doubled
    mysql.max_persistent = 24 ;was -1
    mysql.max_links = 24 ;was -1

    max_execution_time = 45 ; was 30
    max_input_time = 60
    ;max_input_nesting_level = 64
    memory_limit = 128M

    One other clue. It started for me while trying to get the webmail_plus modules running and I had alerts set high to send a lot of email. My emails were not going out (other reasons) but they were draining resources in a pretty major way.

    Hope something here helps someone.
    Erik

    decibel.places’s picture

    I am having the same problem at Bluehost

    I think the solution may be at http://drupal.org/comment/reply/259580/1124846#comment-1124846

    open a support ticket and suggest white-listing http://updates.drupal.org IP (subject to change??) I'm told this may reoccur when firewall is updated, requiring another ticket.

    the IP for http://updates.drupal.org displays as 140.211.166.6

    FWIW, here are some strange log entries I examined

    After this one, I disabled the Views module since I'm not using it, I disabled the image_gallery view because of the "# of items" issue I reported elsewhere #576980: cannot change number of items in image_gallery view - is it Views or Image issue?

    Type	php
    Date	Tuesday, September 15, 2009 - 11:51am
    User	decibel.places
    Location	http://netsperience.org/admin/reports/dblog
    Referrer	http://netsperience.org/admin/reports/updates
    Message	Table 'netsperi_drupalnet.views_display' doesn't exist query: SELECT vid, display_options FROM views_display WHERE display_plugin = 'page' in /home2/netsperi/public_html/sites/all/modules/nodewords/nodewords.module on line 786.
    Severity	error
    Hostname	67.83.70.143
    

    Then there are some other strange messages which seem to suggest that something is being blocked:

    Type	update
    Date	Tuesday, September 15, 2009 - 12:02pm
    User	decibel.places
    Location	http://netsperience.org/admin/reports/updates/check
    Referrer	http://netsperience.org/admin/reports/updates
    Message	Attempted to fetch information about all available new releases and updates.
    Severity	notice
    Hostname	67.83.70.143
    
    Type	page not found
    Date	Tuesday, September 15, 2009 - 12:03pm
    User	decibel.places
    Location	http://netsperience.org/admin/reports/updates
    Referrer	http://netsperience.org/admin/reports/updates
    Message	500.shtml
    Severity	warning
    Hostname	67.83.70.143
    
    Type	page not found
    Date	Tuesday, September 15, 2009 - 12:15pm
    User	decibel.places
    Location	http://netsperience.org/admin/reports/dblog
    Referrer	http://netsperience.org/admin/reports/updates
    Message	500.shtml
    Severity	warning
    Hostname	67.83.70.143
    
    Type	update
    Date	Tuesday, September 15, 2009 - 12:16pm
    User	decibel.places
    Location	http://netsperience.org/admin/reports/updates
    Referrer	http://netsperience.org/admin/settings/actions/manage
    Message	Attempted to fetch information about all available new releases and updates.
    Severity	notice
    Hostname	67.83.70.143
    
    decibel.places’s picture

    I asked Bluehost to whitelist the IP and they sent me this response:

    Dear Customer,

    Do you know what port it is trying to connect to http://updates.drupal.org on? If it's just a web request there shouldn't be anything to whitelist. If it's connecting on a different port we would need to know which port so that it can be opened in our firewall.

    **later**

    nmap shows 3 ports open, it is probably port 80 in use

    (TCP Sequence Prediction: Difficulty=198 looks kind of low?)

    Starting Nmap 5.00 ( http://nmap.org ) at 2009-09-16 09:53 Eastern Daylight Time
    NSE: Loaded 30 scripts for scanning.
    Initiating Ping Scan at 09:53
    Scanning 140.211.166.6 [8 ports]
    Completed Ping Scan at 09:53, 0.65s elapsed (1 total hosts)
    Initiating Parallel DNS resolution of 1 host. at 09:53
    Completed Parallel DNS resolution of 1 host. at 09:53, 0.18s elapsed
    Initiating SYN Stealth Scan at 09:53
    Scanning master.drupal.org (140.211.166.6) [1000 ports]
    Discovered open port 443/tcp on 140.211.166.6
    Discovered open port 80/tcp on 140.211.166.6
    Discovered open port 22/tcp on 140.211.166.6
    Completed SYN Stealth Scan at 09:53, 17.68s elapsed (1000 total ports)
    Initiating Service scan at 09:53
    Scanning 3 services on master.drupal.org (140.211.166.6)
    Completed Service scan at 09:53, 12.78s elapsed (3 services on 1 host)
    Initiating OS detection (try #1) against master.drupal.org (140.211.166.6)
    Retrying OS detection (try #2) against master.drupal.org (140.211.166.6)
    Initiating Traceroute at 09:53
    140.211.166.6: guessing hop distance at 16
    Completed Traceroute at 09:54, 10.31s elapsed
    Initiating Parallel DNS resolution of 14 hosts. at 09:54
    Completed Parallel DNS resolution of 14 hosts. at 09:54, 0.11s elapsed
    NSE: Script scanning 140.211.166.6.
    NSE: Starting runlevel 1 scan
    Initiating NSE at 09:54
    Completed NSE at 09:54, 1.52s elapsed
    NSE: Script Scanning completed.
    Host master.drupal.org (140.211.166.6) is up (0.091s latency).
    Interesting ports on master.drupal.org (140.211.166.6):
    Not shown: 997 filtered ports
    PORT    STATE SERVICE    VERSION
    22/tcp  open  ssh        OpenSSH 5.1 (protocol 2.0)
    |  ssh-hostkey: 1024 88:3d:fc:de:ac:8a:52:15:ad:bb:4d:f9:c5:49:10:7e (DSA)
    |_ 2048 ba:c3:02:6c:75:d7:d4:24:ad:11:ee:3e:19:d6:01:41 (RSA)
    80/tcp  open  tcpwrapped
    443/tcp open  ssl/http   Apache httpd
    |_ sslv2: server still supports SSLv2
    |_ html-title: 403 Forbidden
    Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
    Device type: general purpose|WAP|firewall|printer
    Running (JUST GUESSING) : Linux 2.6.X|2.4.X (95%), Gemtek embedded (91%), Siemens embedded (91%), Linksys Linux 2.4.X (90%), Aastra embedded (88%), Linksys embedded (87%), Xerox embedded (87%)
    Aggressive OS guesses: Linux 2.6.13 - 2.6.27 (95%), Linux 2.6.23 (94%), Linux 2.6.18 (Debian 4.0, x86) (94%), Linux 2.6.15 - 2.6.26 (93%), Linux 2.6.18 - 2.6.27 (93%), Linux 2.6.21 (Arch Linux 0.8, x86) (93%), Linux 2.6.26 (93%), Linux 2.6.27 (Ubuntu 8.10) (93%), Linux 2.6.18 (92%), Linux 2.6.21 (92%)
    No exact OS matches for host (test conditions non-ideal).
    Uptime guess: 159.939 days (since Thu Apr 09 11:21:28 2009)
    TCP Sequence Prediction: Difficulty=198 (Good luck!)
    IP ID Sequence Generation: All zeros
    
    decibel.places’s picture

    Hello,

    I checked in our blacklist and we are not blocking 140.211.166.6. At this point there is no reason to white list it. As Drupal is a third party application, we are only able to offer very limited support on it. My best recommendation would be to contact Drupal and see if they have any ideas what the problem could be.

    Thank you,
    *****
    Technical Support Engineer
    BlueHost.com

    I'm out of ideas....

    decibel.places’s picture

    Bluehost is putting the onus on Drupal - but my Drupal sites on other servers are fine

    just for sh*ts and giggles, I made a fresh default installation of 6.13 at Bluehost

    the ONLY modules enabled are dblog and update

    update fails WTF?

    Details
    Type	update
    Date	Wednesday, September 16, 2009 - 14:04
    User	**** (intentionally masked)
    Location	http://netsperience.org/drupaltest/admin/reports/updates/check
    Referrer	http://netsperience.org/drupaltest/admin/reports/updates
    Message	Unable to fetch any information about available new releases and updates.
    Severity	error
    Hostname	67.83.70.143
    Operations	view
    
    bramface’s picture

    Running traceroute, I see that nero.net is between us and Drupal. I'm going to contact their admin EDITED FOR PRIVACY and see if we can figure out WTF is happening.

    -Bram

    --
    Bram Moreinis
    Greenfield Digital
    http://greenfielddigital.com

    decibel.places’s picture

    I checked traceroute and for me there is also Nero.net - #17 - but I'm not sure why you suspect Nero.net specifically?

    Starting Nmap 5.00 ( http://nmap.org ) at 2009-09-17 17:34 Eastern Daylight Time
    
    Host master.drupal.org (140.211.166.6) is up (0.090s latency).
    
    TRACEROUTE (using proto 1/icmp)
    HOP RTT   ADDRESS
    1   1.00  10.0.1.1
    2   9.00  10.33.64.1
    3   8.00  dstswr1-ge3-2.rh.ehtnny.cv.net (67.59.224.165)
    4   ...
    5   12.00 rtr3-tg10-2.wan.hcvlny.cv.net (64.15.4.5)
    6   11.00 64.15.0.198
    7   ...
    8   15.00 vlan89.csw3.NewYork1.Level3.net (4.68.16.190)
    9   22.00 ae-84-84.ebr4.NewYork1.Level3.net (4.69.134.121)
    10  12.00 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22)
    11  46.00 ae-2-2.ebr1.Chicago1.Level3.net (4.69.132.65)
    12  37.00 ae-6.ebr1.Chicago2.Level3.net (4.69.140.190)
    13  63.00 ae-3.ebr2.Denver1.Level3.net (4.69.132.61)
    14  92.00 ae-2.ebr2.Seattle1.Level3.net (4.69.132.53)
    15  87.00 ge-11-0.hsa2.Seattle1.Level3.net (4.68.105.39)
    16  90.00 unknown.Level3.net (63.211.200.246)
    17  93.00 corv-car1-gw.nero.net (207.98.64.177)
    18  91.00 master.drupal.org (140.211.166.6)
    
    Nmap done: 1 IP address (1 host up) 
    scanned in 32.18 seconds
    

    I am actually at my mother's house for the holiday and using HER ISP and there is still the same problem - so it's not my ISP..

    I have posted more details at #579376: update fails at BlueHost - "Unable to fetch any information about available new releases and updates." - which has been marked as a duplicate with #512218: Checking for available modules fails for most of the modules - perhaps, but the disturbing thing is all these related threads just say the problem goes away by itself without any solution - I suspect that the Drupal updates server is refusing or dropping connections with IPs on shared hosts that are on "suspicious" lists --

    my hosting co (BlueHost) has stopped responding to this ticket, although I told them failure to resolve it will force me to move my site to a server that actually works...

    bramface’s picture

    The hop after nero.net is to ftp.drupal.org, a mirror of which is hosted at osuosl.org where update status looks for module update information (see http://ftp.drupal.org/files/projects/).

    I suspect there must be some "brownlisting" going on ...maybe I ran Drush commands too many times - but I can't figure out who to talk to or how to solve it....

    If this were happening to MANY people I would imagine there would be MANY more posts...

    If anyone knows how to contact the folks who maintain any traffic throttling for ftp.drupal.org (if that is what's happening) I hope they reply....

    --
    Bram Moreinis
    Greenfield Digital
    http://greenfielddigital.com

    decibel.places’s picture

    I opened an issue for this problem and contacted Nero and was told they are not responsible

    in the end, it turned out to be a blacklisting on www4 (whatever that is, I'm not sure) but after this comment about removing my IP from the www4 list update is working

    http://drupal.org/node/579376#comment-2072042

    decibel.places’s picture

    This is an intermittent problem and appears to be a problem with the connection from our servers to the updates.drupal.org I am getting timeouts when I get to nero.net. To confirm this I can see when a successful connection is made to the drupal site and when an outgoing connection fails to get a response from drupal.
    When a successful connection is made I get a connection status such as this almost immediately after making the connection;
    tcp 0 1 69.89.31.246:43918 140.211.166.6:80 LAST_ACK 0 0 -
    When the connection fails to resolve I get a connection where we are sending packets to the destination server but we fail to get a response. Which looks like this;
    tcp 0 1 69.89.31.246:44113 140.211.166.6:80 SYN_SENT XXX 462446649 XXXXX/php5
    After some time it will timeout. After doing some research this seems to be a problem affecting multiple hosts not just Bluehost. I have also done a number of traceroutes from a number of locates and some I get a response to updates.drupal.org (140.211.166.6) and other times the connection dies at 207.98.64.177 corv-car1-gw.nero.net
    I have done extensive tests to make sure that outbound requests are being handled on our end and that the timeouts and functions that are used in php are working correctly.

    nnewton’s picture

    Please open issue on d.o for this. DO NOT CONTACT NERO. Contacting them will do nothing but make them dislike the Drupal community and we really need them to like us. The correct place for complaints about this issue is the d.o infra team. Nowhere else. I have edited your post to remove Davids contact information, while it is available in the whois information it is not appropriate to post here as a possible tech support option. Nero is not tech support and does not answer requests from non-clients. PLEASE DO NOT CONTACT THEM.

    Narayan Newton
    Tag1Consulting
    Drupal Association

    chefobat’s picture

    This is happening to me also. I believe it has to be either php or drupal related. I would bet on php config.

    The way i temporary fixed it on my server is with entry in my hosts file. I suspect that the update script cannot resolve updates.drupal.org to 140.211.166.6. Same was happening with rss server i was trying to connect, it was just not working before I added it in my /etc/hosts. I did a manual update to 6.14 but that didn't help.

    decibel.places’s picture

    The main issue may have been a buggy Drupal release several versions back that creates too many requests to the update server and causes the domain to be blocked. The current releases are fine.

    "www4" is a web node accessed through a load-balancer. nobody accesses it directly - probably the reason why some of my update requests went through and others didn't. This is actually beginning to make sense.

    the solution? Keep your code up to date.

    (haha - but what if you can't connect to the update server, you ask? well, you can tell if you are using the latest version of core which includes the update module, just check the front page of d.o.)

    Drupal Infrastructure advised me:

    ...if this happens to someone they need to contact us. There is nothing a user can do about this except make sure they keep upgraded so they don't get stuck with an old version that has this bug.

    http://drupal.org/project/issues/infrastructure

    gerhard killesreiter’s picture

    The drupal.org infrastructure team tries hard to not block IPs. If you experience issues with accessing updates.drupal.org please first speak to your hoster who might be actually blocking your access.

    leostar’s picture

    I also have same issue with my site and always getting 'Failed to fetch available update data' error after updating to new version. Also I am getting error while updating BUEditor and Imageshack Module..don't know if that is causing the error.

    Leo

    decibel.places’s picture

    leostar:

    First, uninstall those other modules and see if you can connect for updates

    if not post an issue on Drupal Infrastructure and be sure to include your site's domain and/or IP so they can check it
    http://drupal.org/project/issues/infrastructure

    if you are having separate problems with the BUEditor Module you must first search the issues queues to make sure there is not already a thread (and possibly a solution). If you still find nothing, open an issue for each problem - post separate issues on their project issues queues

    http://drupal.org/project/issues/bueditor?status=All&categories=All

    I do not think there is a module for Imageshack - are you using Embedded Media Field?

    http://drupal.org/project/issues/emfield?status=All&categories=All

    cristhian’s picture

    I have drupal 6.14 and when I check for updates it only appears Drupal 6.14, so I dont believe drupal may be blocking my IP because it says "Up to date". I debugged 'update' module and found that in some part of the code projects get lost and aren't even checked for updates..

    cristhian’s picture

    Use CVS deploy when you get your modules with cvs, that was my problem..

    GlobalRaj’s picture

    I am also having same issues. When I checked manually, it is obvious that some of my modules have updates available but when I check from within Drupal's "Available Updates", it comes up with the following.

    No information is available about potential new releases for currently installed modules and themes. To check for updates, you may need to run cron or you can check manually. Please note that checking for available updates can take a long time, so please be patient.

    vacho’s picture

    For my case it worked
    I think the problem is not in drupal, the probles is in the server configuration (firewall block)

    I have a supemecenter to manage the server and I set the "Outgoing connections manager" to allow the server to connect to the server from drupal, add

    ip port count host
    140.211.166.21 80 84 master2.drupal.org
    140.211.166.6 80 84 master.drupal.org

    to allow you to connect. Whether we want to connect to another site outside of your server whith any module...

    If you have other software to manage your server different to SupremeCenter then looking for ways of seeing blocks connections from the inside out.