Bug 565850 – Leftover mirror in namerica

• Product: Mirrors
• Status: RESOLVED FIXED

[Description Michael Cook 2015-11-15 18:33:23 UTC]

Using rsync://rsync.namerica.gentoo.org/gentoo-portage which ends up coming back to rsync://67.212.64.3/gentoo-portage and sits there and does nothing telling about Unauthorized use is prohibited. It also usually moves on to another GTLab IP which does the same thing, which I forgot to note.

[Comment 1 Alex Legler (RETIRED) 2015-11-15 22:16:48 UTC]

The IP address you noted does not match the georgia tech netblock. It belongs to a previous mirror that was removed recently, but not from the region rotation. That is fixed now, GT mirrors seem to be working.

[Comment 2 Michael Cook 2015-12-07 18:09:50 UTC]

128.61.111.9 This IP is also still in the round robin and shouldn't be.

[Comment 3 Alex Legler (RETIRED) 2015-12-07 20:25:58 UTC]

(In reply to Michael Cook from comment #2)
> 128.61.111.9 This IP is also still in the round robin and shouldn't be.

Why? GTlib is a mirror sponsor of Gentoo. Syncing from them is not unauthorized use.

[Comment 4 Michael Cook 2015-12-08 18:12:32 UTC]

(In reply to Alex Legler from comment #3)
> (In reply to Michael Cook from comment #2)
> > 128.61.111.9 This IP is also still in the round robin and shouldn't be.
> 
> Why? GTlib is a mirror sponsor of Gentoo. Syncing from them is not
> unauthorized use.

I have no idea, but this is what I get

>>> Syncing repository 'gentoo' into '/usr/portage'...
>>> Starting rsync with rsync://128.61.111.9/gentoo-portage...
>>> Checking server timestamp ...
---------------------------------------------------------------------------

GEORGIA TECH SOFTWARE LIBRARY

Unauthorized use is prohibited.  Your access is being logged.

Which is exactly what I was getting with 67.212.64.3

[Comment 5 Alex Legler (RETIRED) 2015-12-08 21:17:26 UTC]

(In reply to Michael Cook from comment #4)

You're confusing a few things here.
Your issues with the 67. IP were due to it not being accessible. What is not correct is that this is/was a Georgia Tech IP address. I suspect the next tried server was GTech.

Now, I have resolved the issue with 67. by removing it from our rotation.
I fail to see any issues with Georgia Tech's mirror. I see the notice as well, but get service just fine. It's a notice to tell you 'don't hack us', not a 'keep out' sign.

[Comment 6 Michael Cook 2015-12-08 21:25:45 UTC]

(In reply to Alex Legler from comment #5)
> (In reply to Michael Cook from comment #4)
> 
> You're confusing a few things here.
> Your issues with the 67. IP were due to it not being accessible. What is not
> correct is that this is/was a Georgia Tech IP address. I suspect the next
> tried server was GTech.
> 
> Now, I have resolved the issue with 67. by removing it from our rotation.
> I fail to see any issues with Georgia Tech's mirror. I see the notice as
> well, but get service just fine. It's a notice to tell you 'don't hack us',
> not a 'keep out' sign.

I'll copy the full message next time, but it's the same thing that was happening with the first IP. sync just stalls until I ctrl-z and start again and hope I get a different IP. At the end of the day, hitting that IP is 100% useless for me.

[Comment 7 Michael Cook 2015-12-09 20:33:37 UTC]

Okay, I got that IP again. The furthest this mirror gets me is just saying "receiving incremental file list"

Been like that for a few minutes now.