340445 - 128.61.127.9 changing ip adddress

Status: RESOLVED FIXED

(mozilla.org :: FTP: Mirrors, task)

Description

[Neil Bright]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

I've been asked by our network architect to change the address of our mirror of ftp.mozilla.org from 128.61.127.9 to 128.61.111.9.

I'm responding to http and ftp traffic on both addresses at the moment, can the ftp.mozilla.org rotation be updated to use 128.61.111.9 rather than 128.61.127.9?

Thanks!

Reproducible: Always

Comment 1

[Dave Miller [:justdave]]

Did the direct-access domain name change as well?

You got pulled from the ftp.mozilla.org rotation on Friday when your site was either offline or highly loaded at the time (I got paged saying our nagios couldn't reach your site), and we never got around to adding you back after it came up again.

If you're still getting traffic now, it's probably from our download redirector off the website, and it's using http://trillian.cc.gatech.edu/pub/mozilla.org for the URL prefix.

Also, not sure if you've noticed, but our site is about 500 GB now...  if you want less disk space to worry about, feel free to switch to "mozilla-releases" for the rsync module, which is about 68 GB instead.  That just has the current releases and not all the nightly builds and so forth.  That change will be very likely be forced on you in the next couple weeks (i.e the mozilla-ftp module will be changed to contain that) unless you actively change to a new module we might be setting up to still get everything (but that one will be a whole TB instead of half a TB if we do it) more news on that on the mirrors mailing list in the next few days.

Comment 2

[Dave Miller [:justdave]]

OSL guys aren't directly handling this stuff anymore (not that they can't, but it's not their job anymore)

Comment 3

[Justin Fitzhugh]

is this still an issue or can this be resolved?  trillian.cc appears offline...

Comment 4

[Neil Bright]

trillian.cc.gatech.edu was taken offline years ago, and we've moved to different address space per this ticket.  We used to be part of ftp.mozilla.org, but that DNS rotor seems to have gone away.  Is mozilla still using a download redirector?  GT still does have an active public mirror at:

http://www.gtlib.gatech.edu/pub/mozilla.org
ftp://ftp.gtlib.gatech.edu/pub/mozilla.org
rsync://rsync.gtlib.gatech.edu/mozilla

Comment 5

[Justin Fitzhugh]

thanks for the update - we'll get you added back in.  while we have you here - how much bandwidth can you accept, both normal state and for one day peeks during a release?

as for the ftp mirror, we now host all of ftp.mozilla.org ourselves because we were getting a lot of complaints about the size of the mirror.  we do use dns rr for releases.mozilla.org, and would love to add you into that if you are mirroring the full releases rsync.  let me know what you are pulling, and if you'd like to be added into releases.

Comment 6

[Neil Bright]

Ok, I'm now syncing from ftp-rsync.mozilla.org::mozilla-releases at 0040, 0640, 1240 and 1840.  (All times Eastern/US.)  Is that reasonable?

We can do between 200 mbit normal, bursting to 500 mbit.  Please add 128.61.111.9.

Thanks!

Comment 7

[Justin Fitzhugh]

You are already added into bouncer at a weight of 1000 (generally means how many mb/s you have).  I'll throttle that back assuming the current traffic level is too high.  Do you have numbers on how much mozilla traffic you are seeing?

Also, added you into releases dns rr - let me know how it goes.

Comment 8

[Dave Miller [:justdave]]

If you're rsyncing less frequently than 30 minutes we can't have you in the releases.mozilla.org round robin (and we suggest 15 minutes).  The downloads for extensions go to the releases.mozilla.org domain from addons.mozilla.org, and addons will start sending downloads there 30 minutes after an addon is updated (which means people will get random 404s if you sync less frequently than that).

Comment 9

[Dave Miller [:justdave]]

And we have monitoring on all the releases mirrors, and the oncall sysadmin will get paged if it's more than 60 minutes out of date.

Comment 10

[Neil Bright]

Syncing every 15 minutes seems a bit over the top considering it takes about 3 minutes for me to do a sync when nothing has changed.  I've increased to 30 minute intervals at 10 and 40 past the hour.