search.cpan.org broken?

afoken has asked for the wisdom of the Perl Monks concerning the following question:

Update: Problem on my side. See Re^2: search.cpan.org broken?.

Hi!

Since about two or three weeks, I can't use search.cpan.org. I can ping it, but the web server lets any connection run into a timeout. Did I miss something?

The problem is not in my home network. I have the same problem from the network at work, using a different provider, different DSL box, different firewall.

Ping / traceroute / nmap output from home network:

>ping search.cpan.org
PING cpansearch.perl.org (194.106.223.155) 56(84) bytes of data.
64 bytes from 194.106.223.155: icmp_seq=1 ttl=47 time=46.5 ms
64 bytes from 194.106.223.155: icmp_seq=2 ttl=47 time=46.7 ms
64 bytes from 194.106.223.155: icmp_seq=3 ttl=47 time=46.3 ms
64 bytes from 194.106.223.155: icmp_seq=4 ttl=47 time=45.4 ms
64 bytes from 194.106.223.155: icmp_seq=5 ttl=47 time=46.0 ms
64 bytes from 194.106.223.155: icmp_seq=6 ttl=47 time=45.9 ms
^C
--- cpansearch.perl.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5009ms
rtt min/avg/max/mdev = 45.482/46.191/46.781/0.512 ms

>traceroute search.cpan.org
traceroute to search.cpan.org (194.106.223.155), 30 hops max, 60 byte 
+packets
 1  FIREWALL.XXXXX.XXXXX (192.168.2.1)  0.250 ms  0.224 ms  0.212 ms
 2  DSLBOX.XXXX.XXXXX (192.168.1.1)  1.162 ms  0.804 ms  0.972 ms
 3  loopback1.80.brun.0038-10.ham.de.net.telefonica.de (62.52.200.134)
+  32.915 ms  33.520 ms  31.337 ms
 4  ae3-0.0001.dbrx.03.ham.de.net.telefonica.de (62.53.6.212)  36.774 
+ms  37.664 ms  35.779 ms
 5  ae7-0.0001.corx.01.ham.de.net.telefonica.de (62.53.7.253)  40.599 
+ms  47.198 ms ae7-0.0001.corx.02.ham.de.net.telefonica.de (62.53.8.10
+1)  45.774 ms
 6  ae6-0.0001.corx.02.fra.de.net.telefonica.de (62.53.0.49)  47.904 m
+s  47.318 ms  48.755 ms
 7  bundle-ether16.0002.dbrx.02.fra.de.net.telefonica.de (62.53.26.4) 
+ 50.512 ms  50.886 ms bundle-ether15.0002.dbrx.02.fra.de.net.telefoni
+ca.de (62.53.26.0)  51.859 ms
 8  ae6-0.0001.prrx.11.fra.de.net.telefonica.de (62.53.19.146)  52.064
+ ms  35.731 ms  35.976 ms
 9  ae22.r03.frnkge03.de.bb.gin.ntt.net (62.69.146.85)  36.698 ms  38.
+873 ms  43.012 ms
10  ae-5.r24.londen12.uk.bb.gin.ntt.net (129.250.3.12)  59.027 ms  49.
+697 ms  57.142 ms
11  ae-21.r00.londen10.uk.bb.gin.ntt.net (129.250.4.24)  61.691 ms ae-
+8.r02.londen03.uk.bb.gin.ntt.net (129.250.4.22)  52.055 ms  56.231 ms
12  creative-assembly-0.r00.londen03.uk.bb.ntt.gin.net (83.231.235.146
+)  53.268 ms c4l-0.r02.londen03.uk.bb.gin.ntt.net (83.231.146.230)  5
+4.727 ms  58.395 ms
13  v3708.et-1-0-0.sam.thn.ipv4.net.c4l.co.uk (84.45.27.129)  76.202 m
+s  76.338 ms v3713.et-1-2-0.sam.thn.ipv4.net.c4l.co.uk (84.45.27.138)
+  76.525 ms
14  customer112.c4l.co.uk (84.45.39.130)  66.249 ms  50.498 ms  50.882
+ ms
15  194.106.223.155 (194.106.223.155)  52.729 ms  49.100 ms  58.151 ms
16  194.106.223.155 (194.106.223.155)  52.907 ms !X  51.010 ms !X  54.
+012 ms !X

>nmap -sT -v -v search.cpan.org

Starting Nmap 7.12 ( https://nmap.org ) at 2017-09-20 23:44 CEST
Initiating Ping Scan at 23:44
Scanning search.cpan.org (194.106.223.155) [2 ports]
Completed Ping Scan at 23:44, 0.05s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 23:44
Completed Parallel DNS resolution of 1 host. at 23:44, 0.00s elapsed
Initiating Connect Scan at 23:44
Scanning search.cpan.org (194.106.223.155) [1000 ports]
Discovered open port 80/tcp on 194.106.223.155
Completed Connect Scan at 23:45, 10.11s elapsed (1000 total ports)
Nmap scan report for search.cpan.org (194.106.223.155)
Host is up, received syn-ack (0.052s latency).
Scanned at 2017-09-20 23:44:59 CEST for 10s
Not shown: 998 filtered ports
Reason: 996 no-responses and 2 host-unreaches
PORT    STATE  SERVICE REASON
80/tcp  open   http    syn-ack
113/tcp closed ident   conn-refused

Read data files from: /usr/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned in 10.22 seconds

>
[download]

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Comment on search.cpan.org broken? Download Code

Replies are listed 'Best First'.
Re: search.cpan.org broken? by kcott (Archbishop) on Sep 21, 2017 at 05:07 UTC
G'day Alexander, I use `search.cpan.org` nearly every day: I haven't noticed any problems over recent weeks (or, indeed, recent months). I used it successfully about 20-30 minutes before reading your post. I used it yesterday multiple times over about an eight hour period. My timezone is UTC+10.00 — it's possible I'm just accessing it at a quieter time. Perhaps others based in Europe have had a different experience. I ran a `ping`. Other than a longer roundtrip, I'm getting much the same results as you: $ ping -c8 search.cpan.org PING cpansearch.perl.org (194.106.223.155): 56 data bytes 64 bytes from 194.106.223.155: icmp_seq=0 ttl=48 time=314.191 ms 64 bytes from 194.106.223.155: icmp_seq=1 ttl=48 time=313.335 ms 64 bytes from 194.106.223.155: icmp_seq=2 ttl=48 time=313.465 ms 64 bytes from 194.106.223.155: icmp_seq=3 ttl=48 time=313.455 ms 64 bytes from 194.106.223.155: icmp_seq=4 ttl=48 time=313.425 ms 64 bytes from 194.106.223.155: icmp_seq=5 ttl=48 time=312.850 ms 64 bytes from 194.106.223.155: icmp_seq=6 ttl=48 time=313.020 ms 64 bytes from 194.106.223.155: icmp_seq=7 ttl=48 time=312.897 ms --- cpansearch.perl.org ping statistics --- 8 packets transmitted, 8 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 312.850/313.330/314.191/0.403 ms [download] — Ken	[reply] [d/l] [select]
Re: search.cpan.org broken? by dave_the_m (Monsignor) on Sep 20, 2017 at 21:57 UTC
It worked fine for me when I tried it from my browser just now. Dave.	[reply]
Re^2: search.cpan.org broken? by afoken (Chancellor) on Sep 21, 2017 at 04:53 UTC
Yes, it seems the common factor is Firefox in combination with HTTPS everywhere. For some strange reason, Firefox tries to access search.cpan.org via HTTPS, even after completely removing "HTTPS Everywhere". I can access search.cpan.org from IE, so the problem is somewhere on my side. (I should have tested that before posting.) Update: It seems my FF profile is damaged, a fresh profile can access `http://search.cpan.org/`, but my normal profile forces a redirect to the non-working `https://search.cpan.org/`. Still searching ... Created a new FF profile, without "HTTPS Everywhere". I still wonder what happened, but I won't investigate any further. I've already wasted too much time fixing that problem. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l] [select]

Back to Seekers of Perl Wisdom