Can't Connect to Apache.org Network

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Can't Connect to Apache.org Network

Igal Sapir
Hi all,

I am experiencing a weird network issue and as of ~48 hours ago I can
not connect to the Apache.org network.  I am connected via AT&T Fiber
and spent half the day on the phone with them in vain.  Unfortunately it
is not simple to get a new IP from AT&T (even though it is supposedly a
dynamic address).

I have multiple machines with different operating systems and they all
fail to connect (same outbound IP), so this is not an issue with my
workstation.  When I try to connect from a different location (via a
different ISP) I can connect with no issue.  The only solution I can
think of ATM is to get a VPN service, but I rather find a more permanent
solution.

The last thing I was trying to do was a complete SVN pull with 'git svn
clone' of Tomcat, which failed mid-process with 'error: git-svn died of
signal 11'.  A google search shows results with the title "[INFRA-10509]
Can't connect to SVN - banned? - ASF ... - Apache issues" for
https://issues.apache.org/jira/browse/INFRA-10509 but ironically I can
view that page due to the issue described in this post (I will look it
up through my cellular device).

Any ideas are welcomed.  I include a couple of TraceRoute samples
below.  In the first one, to svn.apache.org, notice that hop 12 is the
destination IP.  WEIRD.

 > tracert svn.apache.org

Tracing route to svn.apache.org [209.188.14.144]
over a maximum of 30 hops:

   1    <1 ms    <1 ms    <1 ms  192.168.254.254
   2     6 ms     7 ms     5 ms
107-216-140-1.lightspeed.irvnca.sbcglobal.net [107.216.140.1]
   3     4 ms     3 ms     3 ms  64.148.105.186
   4     *        *        *     Request timed out.
   5    12 ms     5 ms     6 ms  12.83.38.217
   6     6 ms     6 ms     6 ms  ggr2.la2ca.ip.att.net [12.122.128.101]
   7     *        *        *     Request timed out.
   8     *        *        *     Request timed out.
   9    25 ms    25 ms    25 ms PHOENIX-NAP.bear1.Phoenix1.Level3.net
[4.14.71.174]
  10    25 ms    24 ms    25 ms  108.170.0.29
  11     *        *        *     Request timed out.
  12    25 ms    25 ms    25 ms  209.188.14.144
  13     *        *        *     Request timed out.
  14     *        *        *     Request timed out.
  15     *        *        *     Request timed out.
  16     *        *        *     Request timed out.
  17     *        *        *     Request timed out.
  18     *        *        *     Request timed out.
  19     *        *        *     Request timed out.
  20     *        *        *     Request timed out.
  21     *        *        *     Request timed out.
  22     *        *        *     Request timed out.
  23     *        *        *     Request timed out.
  24     *        *        *     Request timed out.
  25     *        *        *     Request timed out.
  26     *        *        *     Request timed out.
  27     *        *        *     Request timed out.
  28     *        *        *     Request timed out.
  29     *        *        *     Request timed out.
  30     *        *        *     Request timed out.

Trace complete.

 > tracert tomcat.apache.org

Tracing route to tomcat.apache.org [40.79.78.1]
over a maximum of 30 hops:

   1    <1 ms     1 ms     1 ms  192.168.254.254
   2     4 ms     4 ms     3 ms
107-216-140-1.lightspeed.irvnca.sbcglobal.net [107.216.140.1]
   3     3 ms     4 ms     3 ms  64.148.105.186
   4     *        *        *     Request timed out.
   5    11 ms    12 ms     9 ms  12.83.38.221
   6     6 ms     5 ms     5 ms  gar2.la2ca.ip.att.net [12.122.128.133]
   7     6 ms     5 ms     6 ms  12.245.156.22
   8    69 ms    69 ms    66 ms be-71-0.ibr02.lax03.ntwk.msn.net
[104.44.8.108]
   9    66 ms    66 ms    66 ms be-3-0.ibr01.sn4.ntwk.msn.net [104.44.4.5]
  10    66 ms    65 ms    66 ms be-1-0.ibr02.sn4.ntwk.msn.net [104.44.4.204]
  11    65 ms    65 ms    65 ms be-6-0.ibr01.atb.ntwk.msn.net [104.44.4.46]
  12    65 ms    66 ms    66 ms be-1-0.ibr02.atb.ntwk.msn.net [104.44.4.39]
  13    66 ms    67 ms    66 ms be-6-0.ibr01.cnr01.bn6.ntwk.msn.net
[104.44.4.48]
  14    66 ms    65 ms    65 ms ae103-0.icr04.bn6.ntwk.msn.net [104.44.10.8]
  15     *        *        *     Request timed out.
  16     *        *        *     Request timed out.
  17     *        *        *     Request timed out.
  18     *        *        *     Request timed out.
  19     *        *        *     Request timed out.
  20     *        *        *     Request timed out.
  21     *        *        *     Request timed out.
  22     *        *        *     Request timed out.
  23     *        *        *     Request timed out.
  24     *        *        *     Request timed out.
  25     *        *        *     Request timed out.
  26     *        *        *     Request timed out.
  27     *        *        *     Request timed out.
  28     *        *        *     Request timed out.
  29     *        *        *     Request timed out.
  30     *        *        *     Request timed out.

Trace complete.

Thank you,


Igal


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

Igal Sapir
On 6/12/2018 11:41 AM, Igal Sapir wrote:
> <snip/>
>
> The last thing I was trying to do was a complete SVN pull with 'git
> svn clone' of Tomcat, which failed mid-process with 'error: git-svn
> died of signal 11'.  A google search shows results with the title
> "[INFRA-10509] Can't connect to SVN - banned? - ASF ... - Apache
> issues" for https://issues.apache.org/jira/browse/INFRA-10509 but
> ironically I can view that page due to the issue described in this
> post (I will look it up through my cellular device).
OK, perhaps I should have checked that link above on my cell phone
before sending the message (I had a typo there, should read [I can /not/
view that page].

According to Mark in that thread [1], there is a daily threshold and if
you exceed it you get a warning.  "If you trigger three warnings in a
period" you get banned for a long term (weeks).

I did not see any warnings.  The process failed with "error: git-svn
died of signal 11", and seeing no other messages I simply tried it
again, and then again, making it "three times".

@Mark - is it possible to unban the IP or do I need to find a way to get
a new IP address?

Thanks,


Igal

[1] https://issues.apache.org/jira/browse/INFRA-10509


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

Igal Sapir
Update:

On 6/12/2018 11:55 AM, Igal Sapir wrote:

> <snip/>
> According to Mark in that thread [1], there is a daily threshold and
> if you exceed it you get a warning.  "If you trigger three warnings in
> a period" you get banned for a long term (weeks).
>
> I did not see any warnings.  The process failed with "error: git-svn
> died of signal 11", and seeing no other messages I simply tried it
> again, and then again, making it "three times".
>
> @Mark - is it possible to unban the IP or do I need to find a way to
> get a new IP address?
I should have a new IP address soon, so hopefully that part will be
taken care of.

Perhaps it to revisit the thresholds that trigger warnings/bans. The
Tomcat SVN repo might be much larger today than it was when those were
last examined and set.

Also, a ban of a few days can be as effective as a few weeks, yet less
intrusive in case of a false positive as happened here.

Thanks,

Igal

> [1] https://issues.apache.org/jira/browse/INFRA-10509


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

Olaf Kock

On 12.06.2018 23:33, Igal Sapir wrote:
>
> Perhaps it to revisit the thresholds that trigger warnings/bans. The
> Tomcat SVN repo might be much larger today than it was when those were
> last examined and set.

You might want to start at https://github.com/apache/tomcat instead of
pulling down SVN commit by commit. If only for speed.
Unless you want to commit back to svn, that is. (well - I haven't
checked if that git mirror contains the SVN metadata - you'd be lucky if
it does)

Olaf

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

Igal Sapir
On 6/12/2018 3:33 PM, Olaf Kock wrote:

> On 12.06.2018 23:33, Igal Sapir wrote:
>> Perhaps it to revisit the thresholds that trigger warnings/bans. The
>> Tomcat SVN repo might be much larger today than it was when those
>> were last examined and set.
>
> You might want to start at https://github.com/apache/tomcat instead of
> pulling down SVN commit by commit. If only for speed.
> Unless you want to commit back to svn, that is. (well - I haven't
> checked if that git mirror contains the SVN metadata - you'd be lucky
> if it does)

Yes, I need to be able to commit back to SVN on the different branches
(pulling only the trunk was manageable).

Thanks,


Igal

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

markt


On 13/06/2018 01:33, Igal Sapir wrote:

> On 6/12/2018 3:33 PM, Olaf Kock wrote:
>> On 12.06.2018 23:33, Igal Sapir wrote:
>>> Perhaps it to revisit the thresholds that trigger warnings/bans. The
>>> Tomcat SVN repo might be much larger today than it was when those
>>> were last examined and set.
>>
>> You might want to start at https://github.com/apache/tomcat instead of
>> pulling down SVN commit by commit. If only for speed.
>> Unless you want to commit back to svn, that is. (well - I haven't
>> checked if that git mirror contains the SVN metadata - you'd be lucky
>> if it does)
>
> Yes, I need to be able to commit back to SVN on the different branches
> (pulling only the trunk was manageable).

You were banned for > 100,000 page views in a 24 hour period. That is
way more than any reasonably behaving client should be issuing.

I suspect you were pulling down one svn commit at a time. With the ASF
repo, that is pretty much guaranteed to trigger the ban.

See https://wiki.apache.org/general/GitAtApache for details of how to do
this without triggering the ban.

I have removed the ban so you should be good to go.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Can't Connect to Apache.org Network

Igal Sapir
Mark,

On 6/12/2018 11:13 PM, Mark Thomas wrote:
> <snip/>
> You were banned for > 100,000 page views in a 24 hour period. That is
> way more than any reasonably behaving client should be issuing.
>
> I suspect you were pulling down one svn commit at a time. With the ASF
> repo, that is pretty much guaranteed to trigger the ban.

The command I was using (on Windows with MSYS2 git) was:
     git svn clone http://svn.apache.org/tomcat/trunk
And it was a long process until it failed, so you're probably right
about the one-at-a-time.

> See https://wiki.apache.org/general/GitAtApache for details of how to
> do this without triggering the ban.

This link is exactly what I was looking for.  Thanks!

> I have removed the ban so you should be good to go.

I am still banned but my IP should change in a few hours so there's
probably no need to bother with this.

Thank you,


Igal


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]