http://drupal.org/node/549934
Post a follow up:
http://drupal.org/comment/reply/549934#comment-form
Project: Drupal.org infrastructure
Component: Other
Category: support request
Priority: normal
Assigned to: Narayan Newton
Status: active
Updated by: kewlguy
*Nero Issue still exists??*
traceroute to drupal.org (140.211.166.6), 30 hops max, 38 byte packets
1 dc2-vps1-327.liquidweb.com (67.227.191.251) 0.107 ms 0.057 ms
0.051 ms
2 lw-dc2-core3-po4.rtr.liquidweb.com (209.59.157.235) 0.333 ms
0.288 ms *
3 lw-eqx-border5-te1-2.rtr.liquidweb.com (209.59.157.225) 7.892 ms
7.385 ms 7.669 ms
4 64.209.88.185 (64.209.88.185) 6.495 ms 6.495 ms 6.461 ms
5 * te6-2-10G.ar2.CHI2.gblx.net (67.16.132.213) 7.042 ms 6.788 ms
6 te-3-3.car3.chicago1.level3.net (4.68.110.193) 6.549 ms 6.563 ms
7.018 ms
7 ae-31-53.ebr1.Chicago1.Level3.net (4.68.101.94) 14.014 ms * 9.402
ms
8 ae-6.ebr1.Chicago2.Level3.net (4.69.140.190) 9.484 ms 9.862 ms
9.586 ms
9 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 38.350 ms 38.564 ms
37.657 ms
10 ae-2.ebr2.Seattle1.Level3.net (4.69.132.53) 58.443 ms 61.795 ms
54.515 ms
11 * ae-21-52.car1.Seattle1.Level3.net (4.68.105.34) 213.669 ms
207.024 ms
12 eugnor1wce1-univ-of-oregon.wcg.net (64.200.134.198) 120.815 ms
120.942 ms 124.472 ms
13 corv-car1-gw.nero.net (207.98.64.18) 136.453 ms 293.844 ms
121.239 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
Has drupal.org gotten anywhere with these folks? Got any ideas of how I
could make a work around or suggest a change somewhere to my host?
Thanks for listening....lol
kewlguy
Original issue:
------------------------------------------------------------------------
Saturday, August 15, 2009 - 06:14 : Steve Dondley
As of the 13th, I began noticing my cron jobs started to hang and
taking forever. After investigating, I discovered that the update
status was non functional and I was getting "Unable to fetch any
information about available new releases and updates" errors in my
logs.
I ran the following command on the server that hosts my sites: "wget
http://updates.drupal.org/release-history/notify/6.x". The result was
that it just hung after several attempts.
When I run the same command from another server, it downloads the xml
file without a problem.
I have well over one hundred Drupal sites running on my web server.
Perhaps someone thinks I'm being abusive? If so, can someone correct
this or refer me to the person who made that decision? My
server's IP address is 205.237.96.185. Thanks.
Previous comments (76):
------------------------------------------------------------------------
#1 -- Saturday, August 15, 2009 - 06:27 : killes@www.drop.org
http://drupal.org/node/549934#comment-1926972
See my answer on the infra list
------------------------------------------------------------------------
#2 -- Saturday, August 15, 2009 - 11:11 : greggles
http://drupal.org/node/549934#comment-1927600
------------------------------------------------------------------------
#3 -- Saturday, August 29, 2009 - 11:20 : System Message
http://drupal.org/node/549934#comment-1985146
Automatically closed -- issue fixed for 2 weeks with no activity.
------------------------------------------------------------------------
#4 -- Thursday, September 10, 2009 - 08:51 : jptavan
http://drupal.org/node/549934#comment-2026724
I have the same problem with several Drupal site (6.10 or 5.14 + Update
status 5.x-2.3) : the http://updates.drupal.org/release-history [1] url
return a time-out : http://www.damezumari.net/test_outbound.php [2]
<?php
$url = "http://updates.drupal.org/release-history";
if ($fp = fopen($url,"r")){
echo "fopen retourne TRUE pour $url";
}else{
echo "fopen retourne FALSE pour $url";
}
?>
Result : ...failed to open stream: Connection timed out...
I have to disable the Update status module.
My web hosting company support (http://www.ovh.com/ [3]) say they don't
block outbound traffic. Other client have the same problem with Drupal
site.
I have read this info on
http://lists.drupal.org/private/infrastructure/2009-August/016968.html
[4] :
"The problem is as follows: Due to an oversight there was a bug in the
udpate_status module which led - under certain circumstances - to it
requesting updates far more often than neccessary. This in turn led to
problems with drupal.org's stability for normal users. The problem has
been fixed in the code, but we have no way to contact site owners to
tell them to update the code. So the only thing we can do to restore a
sane drupal.org is to block problematic IPs until people notice that
they should be contacting us.
The intention is to work with them in order to get them to upgrade.
"
How to proceeds to unblock my IP (213.186.33.19) ?
I just have to update the module to the latest version (update_status
5.x-2.x-dev ?) and contact infrastructure@drupal.org [5] after that ?
[1] http://updates.drupal.org/release-history
[2] http://www.damezumari.net/test_outbound.php
[3] http://www.ovh.com/
[4]
http://lists.drupal.org/private/infrastructure/2009-August/016968.html
[5] mailto:infrastructure@drupal.org
------------------------------------------------------------------------
#5 -- Friday, September 11, 2009 - 08:35 : Pol
http://drupal.org/node/549934#comment-2031138
Same problem for all my website running Drupal 6 on OVH !!!
Même problème pour moi pour tous mes sites chez OVH !!!
------------------------------------------------------------------------
#6 -- Friday, September 11, 2009 - 09:36 : agojc
http://drupal.org/node/549934#comment-2031416
+1 !
------------------------------------------------------------------------
#7 -- Friday, September 11, 2009 - 13:38 : reptilo
http://drupal.org/node/549934#comment-2032388
Same situation for all my D6 websites hosted by OVH.
I even try to install "Update status advanced settings 6.x-1.x-dev" but
always same answer :
"Unable to fetch any information about available new releases and
updates"
thx to help us !
Drupal 6.13
MySQL 5.0.68
PHP 5.2.10
Apache/2.2.X (OVH)
------------------------------------------------------------------------
#8 -- Friday, September 11, 2009 - 14:12 : leoncarlo
http://drupal.org/node/549934#comment-2032476
Same situation for me,I have my web hosting with OVH, I am using "drupal
6.13" in a lot of web. what can we do? Sorry for my English, I am
Italian
------------------------------------------------------------------------
#9 -- Friday, September 11, 2009 - 18:23 : Narayan Newton
http://drupal.org/node/549934#comment-2033022
Hi all,
The two ips given don't show up in our firewall rules. Any other IPs I
can check for?
-N
------------------------------------------------------------------------
#10 -- Saturday, September 12, 2009 - 03:07 : jptavan
http://drupal.org/node/549934#comment-2033680
213.186.33.18 and 213.186.33.19
------------------------------------------------------------------------
#11 -- Saturday, September 12, 2009 - 05:56 : reptilo
http://drupal.org/node/549934#comment-2033886
213.186.33.19
213.186.33.87
------------------------------------------------------------------------
#12 -- Saturday, September 12, 2009 - 07:20 : rondev
http://drupal.org/node/549934#comment-2033990
213.186.33.2
------------------------------------------------------------------------
#13 -- Saturday, September 12, 2009 - 07:55 : mouameme
http://drupal.org/node/549934#comment-2034042
213.186.33.4 (still mutualized hosting by OVH)
------------------------------------------------------------------------
#14 -- Saturday, September 12, 2009 - 09:07 : jgautier
http://drupal.org/node/549934#comment-2034236
213.186.33.4 (also)
------------------------------------------------------------------------
#15 -- Saturday, September 12, 2009 - 10:49 : leoncarlo
http://drupal.org/node/549934#comment-2034478
94.23.64.16
------------------------------------------------------------------------
#16 -- Saturday, September 12, 2009 - 11:57 : agojc
http://drupal.org/node/549934#comment-2034620
213.186.33.4 also. Waoh ! How many are we sharing the same IP at OVH's
?!!
------------------------------------------------------------------------
#17 -- Saturday, September 12, 2009 - 13:37 : KiamLaLuno
http://drupal.org/node/549934#comment-2034848
If the IP is shared between many web sites, it's clear that the IP is
blocked because there are too many requests coming from the same IP.
That is the reason I preferred to have a static IP for my web site.
------------------------------------------------------------------------
#18 -- Saturday, September 12, 2009 - 13:49 : Damien Tournoud
http://drupal.org/node/549934#comment-2034894
Naranyan confirmed yesterday that we do not block any IP in the
213.186.33.0/24 range. I think this is a configuration issue on the OVH
side.
------------------------------------------------------------------------
#19 -- Sunday, September 13, 2009 - 01:27 : jonjon
http://drupal.org/node/549934#comment-2035774
213.186.33.2 (also)
------------------------------------------------------------------------
#20 -- Sunday, September 13, 2009 - 01:48 : leoncarlo
http://drupal.org/node/549934#comment-2035794
I dont understand, I am with OVH, and I have this IP (94.23.64.16) and I
have the same problem. and
another thing; but what we can do? Change OVH, I have other web with
another hosting company and I never had this kind of problem,MY friend,
what we do?
Sorry for my English and my desolation
------------------------------------------------------------------------
#21 -- Sunday, September 13, 2009 - 02:28 : jptavan
http://drupal.org/node/549934#comment-2035834
"The two ips given don't show up in our firewall rules. Any other IPs I
can check for?
"
Naranyan, could you confirm explicitly that Drupal don't block these IP
? :
94.23.64.16
213.186.33.2
213.186.33.4
213.186.33.18
213.186.33.19
213.186.33.87
------------------------------------------------------------------------
#22 -- Sunday, September 13, 2009 - 02:53 : Gerhard Killesreiter
http://drupal.org/node/549934#comment-2035858
94.23.64.16 is not blocked and none of the others is blocked either.
Try to get a traceroute from the server to drupal.org.
------------------------------------------------------------------------
#23 -- Sunday, September 13, 2009 - 06:37 : leoncarlo
http://drupal.org/node/549934#comment-2036152
In this period I have see that in OVH have change PHP and MYSQL, is
possible that this change have created this problem?
------------------------------------------------------------------------
#24 -- Sunday, September 13, 2009 - 11:21 : leoncarlo
http://drupal.org/node/549934#comment-2036664
Sorry, how can I do a traceroute from the server OVH to drupal.org?
------------------------------------------------------------------------
#25 -- Sunday, September 13, 2009 - 11:54 : Pol
http://drupal.org/node/549934#comment-2036744
My server is on that ip: 213.186.33.16
Still blocked :(
------------------------------------------------------------------------
#26 -- Sunday, September 13, 2009 - 12:56 : Gerhard Killesreiter
http://drupal.org/node/549934#comment-2036830
Yes, a change in the php config could very well explain this problem.
You need to check if your sites can do external http calls at all. Try
to set up an aggregator feed. If that fails, the config issue is to
blame.
------------------------------------------------------------------------
#27 -- Sunday, September 13, 2009 - 13:45 : jptavan
http://drupal.org/node/549934#comment-2036940
"You need to check if your sites can do external at all
"
External http calls work (with the script in #4 and an other server).
I have re-open a ticket with OVH support. We just have to wait for a
reponse (they first said "it's drupal").
------------------------------------------------------------------------
#28 -- Sunday, September 13, 2009 - 14:40 : leoncarlo
http://drupal.org/node/549934#comment-2037082
three days ago I have speek with telefon with OVH and they have said to
me that the problem is of Drupal
------------------------------------------------------------------------
#29 -- Monday, September 14, 2009 - 05:43 : agojc
http://drupal.org/node/549934#comment-2038990
And they seem to reaffirm the same origin to the problem, as seen on :
http://forum.ovh.com/showthread.php?p=311057&posted=1#post311057 [6]
arguing they do not filter the outting connexions...
[6] http://forum.ovh.com/showthread.php?p=311057&posted=1#post311057
------------------------------------------------------------------------
#30 -- Monday, September 14, 2009 - 05:48 : killes@www.drop.org
http://drupal.org/node/549934#comment-2039000
can you ask them to try a traceroute form their servers to drupal.org
and to osuosl.org?
------------------------------------------------------------------------
#31 -- Monday, September 14, 2009 - 06:54 : jptavan
http://drupal.org/node/549934#comment-2039184
OVH support send me the IP for the "outgoing gateway" : 213.251.189.201
to 213.251.189.210
Do you block these IP ?
------------------------------------------------------------------------
#32 -- Monday, September 14, 2009 - 06:58 : killes@www.drop.org
http://drupal.org/node/549934#comment-2039198
We do not block anything in 213.251.*
------------------------------------------------------------------------
#33 -- Monday, September 14, 2009 - 10:54 : jptavan
http://drupal.org/node/549934#comment-2040098
"Try to get a traceroute from the server to drupal.org
"
I ask OVH support for the traceroute :web203:~# ping updates.drupal.org
PING master.drupal.org (140.211.166.6) 56(84) bytes of data.
^C
--- master.drupal.org ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6047ms
web203:~# traceroute drupal.org
traceroute to drupal.org (140.211.166.6), 30 hops max, 40 byte packets
#Internal network section hidden#
6 30g.gblx.gsw-1-6k.routers.chtix.eu (213.186.32.129) 9.291 ms 8.600 ms
8.676 ms
7 xe-8-0-0.edge4.paris1.level3.net (4.68.127.97) 1.526 ms 1.706 ms
1.411 ms
8 ae-34-52.ebr2.Paris1.Level3.net (4.69.139.225) 1.902 ms 1.617 ms
1.484 ms
9 ae-2-2.ebr1.Frankfurt1.Level3.net (4.69.141.234) 14.092 ms 13.602 ms
14.172 ms
10 ae-61-61.csw1.Frankfurt1.Level3.net (4.69.140.2) 18.459 ms
ae-91-91.csw4.Frankfurt1.Level3.net (4.69.140.14) 22.780 ms
ae-71-71.csw2.Frankfurt1.Level3.net (4.69.140.6) 25.669 ms
11 ae-82-82.ebr2.Frankfurt1.Level3.net (4.69.140.25) 14.296 ms
ae-72-72.ebr2.Frankfurt1.Level3.net (4.69.140.21) 20.497 ms
ae-82-82.ebr2.Frankfurt1.Level3.net (4.69.140.25) 21.696 ms
12 ae-41-41.ebr2.Washington1.Level3.net (4.69.137.50) 90.615 ms
ae-43-43.ebr2.Washington1.Level3.net (4.69.137.58) 90.369 ms
ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 92.093 ms
13 ae-2-2.ebr2.Chicago2.Level3.net (4.69.132.69) 114.984 ms 116.021 ms
115.560 ms
14 ae-1-100.ebr1.Chicago2.Level3.net (4.69.132.113) 117.772 ms 116.924
ms 115.863 ms
15 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 137.584 ms 137.206 ms
141.287 ms
16 ae-2.ebr2.Seattle1.Level3.net (4.69.132.53) 185.731 ms 185.282 ms
179.377 ms
17 ge-11-0.hsa2.Seattle1.Level3.net (4.68.105.39) 176.504 ms 172.411 ms
172.643 ms
18 unknown.Level3.net (63.211.200.246) 175.954 ms 176.493 ms 177.903 ms
19 corv-car1-gw.nero.net (207.98.64.177) 178.342 ms 181.338 ms 182.152
ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
NB : chtix.eu is part of OVH network
Tony
~$ host drupal.org
drupal.org has address 140.211.166.6
tony@tony:~$ whois 140.211.166.6
OrgName: Oregon State System of Higher Education
OrgID: OSSHE-1
Address: 1225 Kincaid, UO Campus
NameServer: NS1.NERO.NET
NameServer: OUS.EDU
NameServer: PHLOEM.UOREGON.EDU
RTechHandle: DC80-ARIN
RTechName: Crowe, David
RTechPhone: +1-541-346-1698
RTechEmail: crowed@nero.net
Apparemment leur fournisseur de réseau est NERO
On voit sur le traceroute qu'on atteint le réseau de NERO
(corv-car1-gw.nero.net)
Donc soit c'est un souci au niveau de leur fournisseur, soit on est
bloqué par leur serveur ou leur sous-réseau
Tony
Original messages :
http://forum.ovh.com/showthread.php?p=311137#post311133 [7]
[7] http://forum.ovh.com/showthread.php?p=311137#post311133
------------------------------------------------------------------------
#34 -- Monday, September 14, 2009 - 12:01 : killes@www.drop.org
http://drupal.org/node/549934#comment-2040380
It appears the traceroute ends at nero which is an uplink for the OSL.
I'll discuss the matter with them.
------------------------------------------------------------------------
#35 -- Tuesday, September 15, 2009 - 04:38 : Damien Tournoud
http://drupal.org/node/549934#comment-2043100
OVH confirmed that the issue is on their end
(http://forum.ovh.com/showpost.php?p=311268&postcount=31 [8]).
[8] http://forum.ovh.com/showpost.php?p=311268&postcount=31
------------------------------------------------------------------------
#36 -- Tuesday, September 15, 2009 - 07:57 : jptavan
http://drupal.org/node/549934#comment-2043760
Thank you for your help.
------------------------------------------------------------------------
#37 -- Tuesday, September 15, 2009 - 11:36 : agojc
http://drupal.org/node/549934#comment-2044820
Yes, thank you very much for helping to solve the problem. It works
perfectly now !
------------------------------------------------------------------------
#38 -- Tuesday, September 15, 2009 - 12:38 : KiamLaLuno
http://drupal.org/node/549934#comment-2045038
A fixed problem is marked as fixed.
------------------------------------------------------------------------
#39 -- Tuesday, September 15, 2009 - 14:44 : leoncarlo
http://drupal.org/node/549934#comment-2045604
in my web on OVH dont works, it work for 10 minutes and now again dont
work, I hope that tomorrow It works perfectly
------------------------------------------------------------------------
#40 -- Wednesday, September 16, 2009 - 01:52 : leoncarlo
http://drupal.org/node/549934#comment-2047206
not working
------------------------------------------------------------------------
#41 -- Wednesday, September 16, 2009 - 02:19 : KiamLaLuno
http://drupal.org/node/549934#comment-2047262
@leoncarlo: See comment #35, which reports OVH confirmed the problem is
at their end. Being this the case, there is nothing to do at d.o end.
------------------------------------------------------------------------
#42 -- Thursday, September 17, 2009 - 04:54 : leoncarlo
http://drupal.org/node/549934#comment-2051960
thanks, I'll wait confident
------------------------------------------------------------------------
#43 -- Wednesday, September 30, 2009 - 15:20 : oliverstoney
http://drupal.org/node/549934#comment-2100932
Can you unblock 64.147.160.231 and 64.147.160.230
------------------------------------------------------------------------
#44 -- Wednesday, September 30, 2009 - 17:25 : Narayan Newton
http://drupal.org/node/549934#comment-2101372
I did not find .230 in the rules, but did find .231 and unblocked it.
Please ensure your running a current version of drupal to avoid being
blocked again.
------------------------------------------------------------------------
#45 -- Thursday, October 1, 2009 - 08:05 : bkudrle
http://drupal.org/node/549934#comment-2103336
I have this same problem for a client, but she is using a different
hosting company - inmotionhosting.com. I have tried installing numerous
Drupal versions from scratch (6.13 being the latest try - earlier I used
6.14). The provider said that they are not blocking outgoing requests.
So what is the procedure that I should use at this point? The shared IP
for the site is 74.124.210.84. The support at the hosting provider says
that this shared IP would be the one that would have the outgoing
request.
------------------------------------------------------------------------
#46 -- Thursday, October 1, 2009 - 14:25 : Narayan Newton
http://drupal.org/node/549934#comment-2104910
I'm not showing anything for '74.124.210.84', but did find
74.124.195.152. Can you double check with the hosting company if that IP
address is anything significant for them.
-N
------------------------------------------------------------------------
#47 -- Thursday, October 1, 2009 - 15:37 : bkudrle
http://drupal.org/node/549934#comment-2105132
Thanks so much for your reply. The provider said that the 74.124.195.152
IP was theirs but should not affect requests from my site. They did also
say, though, that IP 74.124.198.63 "is also assigned to your server and
does answer requests for it". Could that be a problem? Thanks again for
your time in this.
------------------------------------------------------------------------
#48 -- Thursday, October 1, 2009 - 15:58 : KiamLaLuno
http://drupal.org/node/549934#comment-2105218
It seems both the IPs are own from the same company, but I don't see any
relation between them (nor the traceroute passes through 74.124.195.152
to go to 74.124.210.84).
sunradio:~ Kiam$ whois 74.124.195.152
Corporate Colocation Inc. CORPCOLO-NET03 (NET-74-124-192-0-1)
74.124.192.0 - 74.124.223.255
InMotion Hosting CORPCOLO-NET-74-124-194-0-23 (NET-74-124-194-0-1)
74.124.194.0 - 74.124.195.255
sunradio:~ Kiam$ whois 74.124.210.84
Corporate Colocation Inc. CORPCOLO-NET03 (NET-74-124-192-0-1)
74.124.192.0 - 74.124.223.255
InMotion Hosting CORPCOLO-NET-74-124-210-0-23 (NET-74-124-210-0-1)
74.124.210.0 - 74.124.211.255
sunradio:~ Kiam$ traceroute -P ICMP 74.124.210.84
traceroute to 74.124.210.84 (74.124.210.84), 64 hops max, 72 byte
packets
...
22 te1-7.cr01.ord01.us.mzima.net (69.174.120.74) 125.948 ms
126.552 ms 124.145 ms
23 te0-0.cr01.dfw01.us.mzima.net (69.174.120.14) 157.431 ms
146.762 ms 156.372 ms
24 te1-1.cr01.phx01.us.mzima.net (69.174.120.37) 192.440 ms
179.271 ms 179.821 ms
25 te1-1.cr01.lax02.us.mzima.net (69.174.120.33) 189.532 ms
179.549 ms 180.131 ms
26 xe1-0.cr01.lax03.us.mzima.net (216.193.255.186) 179.651 ms
193.076 ms 179.975 ms
27 ge0-corpcolo.cust.lax03.mzima.net (72.37.172.122) 180.110 ms
179.511 ms 179.066 ms
28 biz51.inmotionhosting.com (74.124.210.84) 179.648 ms 179.335
ms 179.725 ms
sunradio:~ Kiam$ traceroute -P ICMP 74.124.195.152
traceroute to 74.124.195.152 (74.124.195.152), 64 hops max, 72 byte
packets
...
21 nyiix.ge2-6.cr01.lga01.mzima.net (198.32.160.169) 107.078 ms
107.049 ms 107.804 ms
22 te1-1.cr01.iad01.us.mzima.net (69.174.120.62) 112.434 ms
121.378 ms 125.634 ms
23 te1-3.cr01.atl01.us.mzima.net (69.174.120.53) 125.409 ms
125.091 ms 125.824 ms
24 te0-1.cr01.dfw01.us.mzima.net (69.174.120.49) 153.809 ms
143.746 ms 143.595 ms
25 te1-1.cr01.phx01.us.mzima.net (69.174.120.37) 177.930 ms
178.810 ms 177.120 ms
26 te1-1.cr01.lax02.us.mzima.net (69.174.120.33) 180.536 ms
179.075 ms 179.601 ms
27 xe1-0.cr01.lax03.us.mzima.net (216.193.255.186) 178.852 ms
191.738 ms 180.054 ms
28 ge0-corpcolo.cust.lax03.mzima.net (72.37.172.122) 179.581 ms
178.269 ms 180.098 ms
29 205.134.254.17 (205.134.254.17) 179.923 ms 178.227 ms
180.267 ms
30 vps932.inmotionhosting.com (74.124.195.152) 179.250 ms 181.855
ms 180.064 ms
------------------------------------------------------------------------
#49 -- Thursday, October 1, 2009 - 17:24 : bkudrle
http://drupal.org/node/549934#comment-2105490
Thanks again for your work.
And can I assume that the other IP address they gave me - 74.124.198.63
- also is not blocked?
------------------------------------------------------------------------
#50 -- Thursday, October 1, 2009 - 18:35 : leostar
http://drupal.org/node/549934#comment-2105698
Hi
I am also facing the same issue with my site Failed to "fetch available
update data". Site is hosting on Godaddy and the IP is 72.167.232.196.
Can you please see if this ip is blocked.
Thanks,
Leo
------------------------------------------------------------------------
#51 -- Friday, October 2, 2009 - 20:43 : javierdiaz
http://drupal.org/node/549934#comment-2109358
Hello,
LIke others above, I'm experiencing :Unable to fetch any information
about available new releases and updates."
Can you please see if these IP's are blocked
66.40.3.4
66.40.8.100
66.40.56.80
66.40.56.79
I'm glad it's not just me with this issue.
THanks,
Javier
------------------------------------------------------------------------
#52 -- Saturday, October 3, 2009 - 10:43 : bkudrle
http://drupal.org/node/549934#comment-2110594
Would it be possible and feasible (without compromising security) to
post the blocked IPs somewhere so as to minimize your work in looking
all of these up? Just a thought...
------------------------------------------------------------------------
#53 -- Monday, October 5, 2009 - 14:00 : jjkiesch
http://drupal.org/node/549934#comment-2117588
I am not able to get updates either right now. IP address is
205.178.145.65. It is a Network Solutions server.
Can you check to see if it is blocked?
Thanks!
------------------------------------------------------------------------
#54 -- Wednesday, October 7, 2009 - 07:17 : jfeiler
http://drupal.org/node/549934#comment-2123752
Also problems with a Network Solutions server at 205.178.145.65. Can
you check? We're not getting status updates and timing out on feeds from
d.o.
------------------------------------------------------------------------
#55 -- Thursday, October 8, 2009 - 07:33 : BrightBold
http://drupal.org/node/549934#comment-2127690
Like bkudrle I am with InMotion and having this problem on both Drupal
sites (one 6.13 and one 6.14) I have hosted there. The server is
reporting as 74.124.198.60. Thanks for your help.
------------------------------------------------------------------------
#56 -- Thursday, October 8, 2009 - 09:34 : KiamLaLuno
http://drupal.org/node/549934#comment-2128134
The report is marked as fixed; if you don't change the status, it is
difficult somebody will look into it.
------------------------------------------------------------------------
#57 -- Saturday, October 10, 2009 - 08:40 : atelier
http://drupal.org/node/549934#comment-2135308
Please check 72.249.95.146. Thank you.
* EDIT *
Please also check:
72.249.95.147
72.249.95.148
72.249.95.149
------------------------------------------------------------------------
#58 -- Monday, October 12, 2009 - 18:08 : Narayan Newton
http://drupal.org/node/549934#comment-2143096
I've unbanned all the IPs listed above that I could find.
72.249.95.146
74.124.195.152
I'm afraid none of the other IPs were found in our rules.
------------------------------------------------------------------------
#59 -- Tuesday, October 13, 2009 - 06:58 : jfeiler
http://drupal.org/node/549934#comment-2144868
Were there only the two you listed? How do we address the issues for all
of the other IPs? Someone suggested posting a list of banned IPs, and
this appears to do so (If it's only those two). Because a large number
of IPs have been listed on this thread, there must be something going
on. (I checked and I'm still not able to access updates.)
Many of us pay attention to status updates. I'm not sure there's any
way of knowing how many Drupal installations don't know/understand the
importance of these updates, so I don't think it's possible to know how
many people are now not getting status update messages. This has the
potential to really impact Drupal negatively.
Any suggestions for how to proceed?
------------------------------------------------------------------------
#60 -- Tuesday, October 13, 2009 - 12:13 : Jazzy
http://drupal.org/node/549934#comment-2146454
Hi!
Can you please check 81.169.145.81, 81.169.145.74, 81.169.145.65 and
81.169.145.66?
Thanks!
------------------------------------------------------------------------
#61 -- Wednesday, October 14, 2009 - 11:04 : escoles
http://drupal.org/node/549934#comment-2150718
I'm also unable to get updates. This is 6.14 on a VPS that's brand new
to us.
Can you please check:
206.188.208.40
Host is NetSol.
What's the protocol for this? Should we be submitting individual
issues? Would that be easier for you to triage?
------------------------------------------------------------------------
#62 -- Wednesday, October 14, 2009 - 13:35 : jfeiler
http://drupal.org/node/549934#comment-2151370
This is at least the third issue with NetSol that has been posted
here--but there have been other providers cited. I concur--what is the
best way to handle this?
------------------------------------------------------------------------
#63 -- Thursday, October 15, 2009 - 08:20 : escoles
http://drupal.org/node/549934#comment-2154516
I'm getting through fine now - thanks. (if it's not something you did,
then thanks for listening.)
Narayan et al. -- as d.o is providing a very useful service w.r.t.
update checking, I'm sure most of us will be willing to carry some water
to smooth out your processes. Let us know what you would like us to do
to make this easier for you.
------------------------------------------------------------------------
#64 -- Friday, October 16, 2009 - 06:39 : jfeiler
http://drupal.org/node/549934#comment-2158706
We're still not getting updates through a NetSol server at
205.178.145.65. Is there any way to let people know what is or isn't
happening? There clearly are some problems and we could track them down
but we need to know what is happening on the d.o. side. Are these
blocked? Are they not listed or not found? We also need to know when
problems have been resolved so a pattern can be found.
Not being able to rely on Drupal's automatic update checking in
(unknown) circumstances, is a major vulnerability for many people
------------------------------------------------------------------------
#65 -- Monday, October 19, 2009 - 11:05 : Narayan Newton
http://drupal.org/node/549934#comment-2168602
Hi jfeiler,
We have no IP's matching that in our fw rules and no other blocking
takes place on our side. In fact, there are no ips with the prefix
205.178. I'd be happy to help you debug this, but as of this point I
have no real options :).
-N
------------------------------------------------------------------------
#66 -- Monday, October 19, 2009 - 15:05 : jfeiler
http://drupal.org/node/549934#comment-2169454
I've confirmed with NetSol that the IP address for our hosted site is
205.178.145.65 and that they're not using another address.
I think the error is happening in opening the connection inside
drupal_http_request in common.inc. The line I'm suspicious of is
case 'http':
$port = isset($uri['port']) ? $uri['port'] : 80;
$host = $uri['host'] . ($port != 80 ? ':'. $port : '');
$fp = @fsockopen($uri['host'], $port, $errno, $errstr, 15);
<--this line
break;
I saw a bug report complaining about the built-in 15 second timeout and
I changed it to 45 on a spare installation of mine but it still failed.
There are times when connections are taking a long time so I'm wondering
if I should just try to bump that up more.
I've also not been able to run aggregator against d.o. feeds, and I
thought they were related issues--when I poked around in the code I saw
(not surprisingly) that both of them are coming through
drupal_http_request so that is probably the issue.
Any suggestions are welcome!
------------------------------------------------------------------------
#67 -- Monday, October 19, 2009 - 15:16 : jfeiler
http://drupal.org/node/549934#comment-2169484
There may be another IP address involved: 24.176.138.44.
------------------------------------------------------------------------
#68 -- Monday, October 19, 2009 - 15:44 : Narayan Newton
http://drupal.org/node/549934#comment-2169620
I'm afraid I can't find that IP either. Could you try a telnet or nc
connection on port 80 to 140.211.166.6 and 140.211.166.61 and let me
know which one works. Thanks.
------------------------------------------------------------------------
#69 -- Monday, October 19, 2009 - 16:20 : jfeiler
http://drupal.org/node/549934#comment-2169732
Both work with nc. I'm going to go through another avenue which could be
interfering with the message and then I'll increase the timeout (but I
don't think it's timing out for performance, just not getting through).
It's got to be something simple, and it's a fluke that it happened when
you blocked some IPs on d.o. and we went off on (I think) a wild goose
chase.
------------------------------------------------------------------------
#70 -- Thursday, October 22, 2009 - 19:44 : BrightBold
http://drupal.org/node/549934#comment-2181934
Yea! I logged into my site today to be greeted with 11 (count-em, 11!)
recommended updates. If you did something to make this magic happen,
thanks!
------------------------------------------------------------------------
#71 -- Saturday, October 24, 2009 - 11:55 : Logan Bear
http://drupal.org/node/549934#comment-2187336
Can you check IP 174.132.165.2 ? I'm having the same problem. Thanks.
------------------------------------------------------------------------
#72 -- Wednesday, October 28, 2009 - 09:05 : belulo
http://drupal.org/node/549934#comment-2201320
Hello!
I have a same problem. Can you help me: 94.199.180.17?
Thx!
------------------------------------------------------------------------
#73 -- Sunday, November 1, 2009 - 11:09 : MarioN70
http://drupal.org/node/549934#comment-2214454
Please Narayan, you can check if the IP 74.81.81.100 is it blocked?, I
cannot update Drupal.
Thanks.
------------------------------------------------------------------------
#74 -- Monday, November 2, 2009 - 20:03 : bbenjamin602
http://drupal.org/node/549934#comment-2219628
Having the same issue with Hostmonster who uses Bluehost. Updating 6.14
renders the same error. I have dedicated IP number 66.147.240.88.
Thanks,
Bruce
------------------------------------------------------------------------
#75 -- Tuesday, November 3, 2009 - 09:47 : jfeiler
http://drupal.org/node/549934#comment-2221326
Can you check this range of IP addresses? 205.178.145.64 to
205.178.145.159 We still cannot connect.
------------------------------------------------------------------------
#76 -- Wednesday, November 4, 2009 - 20:31 : WebNewCastle
http://drupal.org/node/549934#comment-2228382
Updated: Please ignore the previous request. It appears that the
hosting provider made a block on the firewall. I'm still looking into
why that might be the case, but apparently in my case that is what the
issue was after all.
Hello,
Can someone check 74.54.164.189 as well? As of a couple days ago, I
also can't get updates and this is the first time I've ever had an
issue. It doesn't appear to be the drupal_http_request_fails variable
as far as I can tell. If it did get blocked, can someone also tell me
how to avoid this?
Thanks,
Matt
--
[ infrastructure | http://lists.drupal.org/mailman/listinfo/infrastructure ]
Posts
0 评论:
Post a Comment