Skip to content

Access to cran.us.r-project.org

3 messages · Douglas Bates, A.J. Rossini, Peter Dalgaard

#
I am the maintainer of one of the CRAN mirrors in the U.S.,
cran.us.r-project.org.  It appears that this site has been
inaccessible since Friday.

This has me puzzled because I can connect to the same machine through
ssh and I can see that the http daemon (apache) is running.  In fact I
can make an http connection from this machine to this machine and from
other machines on any of our subnets to this machine.

My only theory is that something has changed at the interface between
our network and external networds so that it no longer forwards
incoming packets to port 80.  I can't check this easily myself because
my outside connection is from a computer running Windows and I don't
know anything about network diagnostics under Windows.

Could someone tell me 
 a) Does this site indeed appear to be down?
 b) If you try to trace the route to this site, where does the
 roadblock appear to be?
 c) Is there a way of finding out if the problem is specific to port
 80?
#
DB> I am the maintainer of one of the CRAN mirrors in the U.S.,
    DB> cran.us.r-project.org.  It appears that this site has been
    DB> inaccessible since Friday.

    DB> This has me puzzled because I can connect to the same machine
    DB> through ssh and I can see that the http daemon (apache) is
    DB> running.  In fact I can make an http connection from this
    DB> machine to this machine and from other machines on any of our
    DB> subnets to this machine.

    DB> My only theory is that something has changed at the interface
    DB> between our network and external networds so that it no longer
    DB> forwards incoming packets to port 80.  I can't check this
    DB> easily myself because my outside connection is from a computer
    DB> running Windows and I don't know anything about network
    DB> diagnostics under Windows.

    DB> Could someone tell me a) Does this site indeed appear to be
    DB> down?  b) If you try to trace the route to this site, where
    DB> does the roadblock appear to be?  c) Is there a way of finding
    DB> out if the problem is specific to port 80?

Traceroute gets there. 

16  a0.uwisc.bbnplanet.net (4.24.223.22)  109.324 ms  109.628 ms
108.532 ms
17  r-peer-WNMadison-gw.net.wisc.edu (216.56.1.18)  110.048 ms
109.648 ms  109.921 ms
18  r-macc.net.wisc.edu (144.92.128.129)  111.303 ms  109.753 ms
109.904 ms
19  144.92.128.196 (144.92.128.196)  112.013 ms  112.497 ms  113.195
ms
20  e1-2.foundry2.cs.wisc.edu (128.105.1.6)  111.985 ms  113.530 ms
112.534 ms
21  franz.stat.wisc.edu (128.105.174.95)  112.077 ms  112.941 ms
111.896 ms
root@jeeves:~
# # command used:    traceroute cran.us.r-project.org



telnet'ing to port 80 "hangs".  Lynx doesn't work either.

I could nmap it, but don't want to be viewed as a hacker... (I'd tell
you the ip-address of the machine in advance).

I think it might be a local config problem?

best,
-tony
#
rossini@blindglobe.net (A.J. Rossini) writes:
developer.r-project.org is equally dead. For the same reason of
course. It *is* possible to connect locally, e.g.

lynx developer.r-project.org

works fine when issued on Franz. The apache server seems to have been
reset at 06:25 this morning and also at 11.19 yesterday.