www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11614) archive.apache.org rejecting requests from 54.153.17.229
Date Thu, 07 Apr 2016 19:25:25 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230894#comment-15230894
] 

Philip Zeyliger commented on INFRA-11614:
-----------------------------------------

[~cml],

Thanks for the response!  After talking to our network engineers, I now know that most of
our requests are coming through a NAT gateway at 54.153.17.229.  We don't believe that our
usage today is any different than it was, say, last week, but obviously if we're the culprit,
I'm at your service to chase it down and fix it within my organization (Cloudera).

Many thanks!

> archive.apache.org rejecting requests from 54.153.17.229
> --------------------------------------------------------
>
>                 Key: INFRA-11614
>                 URL: https://issues.apache.org/jira/browse/INFRA-11614
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: HTTP Server
>            Reporter: Philip Zeyliger
>            Assignee: Chris Lambertus
>
> Hi there,
> We're experiencing connection timeouts to {{archive.apache.org}} from EC2 machines in
us-west-1.  (An example IP is 54.153.17.229.)  We're getting these errors in connection with
building some Apache projects from source (like https://github.com/apache/sqoop/blob/branch-1.99.5/dist/pom.xml#L163).
> We're obviously working on redirecting our builds to point at something different, but
we'd love to learn definitively that Apache has, in fact, blocked a chunk of EC2, and whether
it's possible to lift that block.
> Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message