Unable to fetch any information about available new releases and updates

Same thing here in a new install.

Pepe

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

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

:-)
José

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.

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.

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

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.

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....

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

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...

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.

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.

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

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

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

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.