Posted by murari on December 3, 2009 at 9:15am
Jump to:
| Project: | Drupal.org infrastructure |
| Component: | Other |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | Drupal update |
Issue Summary
I've been getting this error since the last 2 weeks. I dont know if it is due to some module that i have installed, or is it because updates.drupal.org has blacklisted my IP?
It Would be nice to get the updates report working again.. thanks.
Comments
#1
I have the same problem since last night. I noticed that Drupal's site was down a couple times and the "Failed to fetch available update data" message started to show afterward...hope to get the updates soon too...
#2
I just noticed the problem after upgrading to 6.15 ... any ideas?
#3
I also have it on 1 module only since the update to 6.15 - content access.
I haven't done anything else.
#4
I ran cron manually and problem solved.
#5
#6
I have marked #663564: Unable to fetch any information about available new releases and updates. as duplicate of this report.
#7
Same here, I got this message after upgrading to 6.15 on my local test machine.
So I don't want to upgrade on the prod site.
#8
Running cron does appear to run cron, and states "cron ran succesfully". However the issue still remains and the alert that I need to run cron stay visible. This is annoying. Other than de-activating every module, one at a time, and re-activating them independently, has anyone found a solution to this?
#9
I can't fetch updateseither on any of my domains. I contacted my webhost -- nothing is blocking it on their end. I don't recall making any change when this happened. I have multiple website and the problem persists on all of them.
#10
I also got this problem since I installed 6.14 like two months ago. I upgraded to 6.15 when it was released and I still get the same error... This didn't happen on other drupal websites I made on the same Server some months ago.
#11
Same here. Just started today, and it's on 6.14 (which I have had since it was released). Not sure why it's just starting now...
#12
Subscribe - I am also getting this problem on NetworkSolutions client site.
#15
I'm also seeing this on two websites hosted at Network Solutions. But I do not have this problem on a website on a dedicated server at Rackspace.
I also have the symptom that the Available Updates report is empty. It doesn't even list the version of Drupal installed or any of the installed modules.
#16
Me three: NetSol, Drupal 6.14 and now Drupal 6.15.
#17
In 99% if all cases the block is not from our side but from the network provider you are on. Please contact them and find out about this.
#18
I too have this issue with drupal 6.15 and I've worked with the server admin who states nothing is blocked. Agregator feeds work. So update should work too shouldn't it? Unable to fetch any information about available new releases and updates. Is the only error I can find in the logs.
#19
subscribing
#20
This problem recently started on my site as well. Any info would be greatly appreciated.
#21
We currently do not block any IPs. So it is likely a problem at your service provider.
#22
I don't mean to be rude, but it doesn't seem logical to me to conclude that there is no possible way that it could be a problem with Drupal. My host and service provider have been the same for years, and this issue just started a few weeks ago. I imagine that this is true for many others facing the same issue.
Can you think of any way to test this problem to understand if the issue resides in Drupal itself or if the IP is truly blocked?
#23
FWIW, we're on Media Temple and we, too, have just started seeing this error.
#24
Gerhard Killesreiter reported that the list of banned IPs has been cleaned, and it doesn't contain any IPs; therefore, no IPs are blocked from Drupal.org side.
May you provide the output of the command line executed from the site that is being blocked?
#25
I'm not a Drupal expert by any stretch, but I took a shot at trying to trace back through Drupal's code to figure out where things are going wrong on my site.
I found what I believe to be a problem in the "_update_refresh()" function in the file update.fetch.inc. In the block of code below, the condition (isset($xml->data)) is never true when I try to manually update my site.
if (empty($fail[$fetch_url_base]) || count($fail[$fetch_url_base]) < $max_fetch_attempts) {
$xml = drupal_http_request($url);
if (isset($xml->data)) {
$data[] = $xml->data;
}
else {
// Connection likely broken; prepare to give up.
$fail[$fetch_url_base][$key] = 1;
}
}
else {
// Didn't bother trying to fetch.
$fail[$fetch_url_base][$key] = 1;
}
}
I am trying now to trace through the drupal_http_request function to see where everything is going wrong. Any thoughts would be greatly appreciated.
#26
Ok, so I've traced my problem back to the drupal_http_request() function.
On line 458 of common.inc, we have the line "$fp = @fsockopen($uri['host'], $port, $errno, $errstr, 15);" This always fail when I try to fetch status updates.
The error string ($errstr) that is returned is "Network is unreachable"
I would love any thoughts on what could be going on here. I don't know what much of this code means, only that this is the place that things seem to be going badly for my site.
#27
Your hoster does not allow your php install to connect to the outside world.
#28
... Alright, I was going to be nice and not say anything because I personally have not seen the issue again since my original post... however...
To say that because drupal.org is not blocking any ip addresses the issue must lie with your host is just plain rude and in no way is an attempt to resolve or "fix" the issue. Sounds more like the status should have been changed to "won't fix". FYI the server I am running on is a physical box in my workplace and we were not at any point blocking ourselves from the outside world.
While I understand that in theory the sites should be receiving this information, the fact is that it is not working for some of us. (I am including myself because I would like to know where the issue laid).
Instead of stating the the issue has been resolved, how about considering what is required for this data to make it to our servers and possible places to look like modules or settings that may be interfering?
#29
We are the Drupal.org infrastructure team. We work hard to keep drupal.org running. We do this in our spare time. We are _not_ your babysitter. If your computer can't connect to our network and we have taken reasonable steps to ensure that this is not our fault (ie by ensuring we do not block your IP), the remainder is _your_ problem.
And now please crawl back under your stone.
#30
Ok then instead of saying "fixed", you could have said just that and/or move it to a different support queue. All you had to do was say that we were looking for support under the wrong place...
#31
@killes@www.drop.org:
Hey man, I'm sorry if I came off like a punk. Clearly I'm the one responsible for debugging my site, and we all sincerely appreciate the hard work that goes into keeping Drupal.org healthy.
All I'm trying to say is that whether or not the problem is actually on Drupal's end, it's still a problem affecting some of us in the community and we have no idea why. I would just like to get to a point where this thread can serve as a means to check other steps in the process of connecting to drupal.org where things could be going wrong.
Anyway - I've done some more digging, and it seems that some web hosts block PHP fsockopen calls for security reasons. This is the call that the drupal_http_request() function uses.
I've reached out to my host to understand if they recently changed their policy on allowing these types of PHP calls. I'd suggest that others do the same.
#32
While I don't doubt that policies can change quickly from one day to another, it still wouldn't explain intermittent issues like what I experienced...
Let us know what your webhost responds with.
#33
My host originally informed me that drupal.org was not being blacklisted. They also confirmed that they do allow fsockopen calls.
Despite the first point, they went ahead and added the drupal.org IP address to the server whitelist, and everything's working fine for me now (go figure).
#34
Automatically closed -- issue fixed for 2 weeks with no activity.
#35
Well my site was working just fine with showing available updates before this big switch to the new setup on the drupal.org site, now I get 5-6 modules that show their correct status, and all others come up with the fail to fetch update data, including core status.
#36
I've been having issues in at least 5 different setups (really-low-traffic sites + all on personally controlled servers over simple aDSL lines) using 3 different ISPs. I admit that this only seems to happen when the amount of modules in each setup is quite large + most of the times I also check for updates on disabled ones. I've had this issue for far too long without reporting anything, but now I got tired of having this issue where only some of the modules/themes are retrieving update info and the rest of them simply display 'Failed to fetch available update data'. I was not sure if this belongs here or in Drupal core under the 'update system' or the 'update.module' component, so please enlighten me...
Some times I need to click the '(Check manually)' link several times before finally receiving update info for all of them. Some of the times even after this persisting manual check there'll be one or two of them still not receiving update info. This is frustrating!
So, I need to ask: what happens if during the whole checking-for-updates procedure something goes wrong and no update info is retrieved? Does it try a second or third time or does it simply fail gracefully? Is there any setting someplace that I somehow missed so that I can force it to keep trying every while for the modules/themes it failed? Anyone aware of any feature request filed for this?
Thanx in advance and sorry for the question attack ;)
#37
@klonos Those questions are really about Drupal core software, not the drupal.org infrastructure.
#38
Thanx for taking the time to reply Michael. I kinda new beforehand...
...but during my searches this issue came up as the most relevant and I didn't want to start a fresh issue in case one was already open for the same thing. I did see this reply in #575044: "Failed to fetch available update data" at /admin/reports/updates that lead me here though. Anyways, I think I've found that my issues better fit #512218: Checking for available modules fails for most of the modules. Sorry for 'polluting' this issue.