289264 - mozilla.cs.utah.edu (155.98.64.83) is not updating

Status: VERIFIED WORKSFORME

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

Description

[Nick Thomas [:nthomas] (UTC+12)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050405 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050405 Firefox/1.0+

A user on the mozillazine forums has pointed out that the mirror at 155.98.64.83
has stale Firefox nightlies - the latest are from the 23-Mar.
cf: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Original report: http://forums.mozillazine.org/viewtopic.php?t=246530

Quick inspection does not yield any files with dates after 23 March so it would
appear that the mirror is no longer syncing.

Reproducible: Always

Steps to Reproduce:

Comment 1

[seth]

The link you provided only shows the problem if you happen to get the right ftp
mirror.

Try this one:

http://155.98.64.83/pub/mozilla.org/firefox/nightly/latest-trunk/

or

http://mozilla.cs.utah.edu/pub/mozilla.org/firefox/nightly/latest-trunk/

Comment 2

[Klaus P. Kuhlemann]

I can confirm this, I got this mirror several times in the last 2 weeks typing 
ftp.mozilla.org.

Comment 3

[Dave Miller [:justdave]]

utah has been removed from the round-robin until this gets fixed.

Comment 4

[Worcester12345]

(In reply to comment #3)
> utah has been removed from the round-robin until this gets fixed.

Should this bug then be marked as fixed, invalid, wfm?

Comment 5

[Dave Miller [:justdave]]

(In reply to comment #4)
> (In reply to comment #3)
> > utah has been removed from the round-robin until this gets fixed.
> 
> Should this bug then be marked as fixed, invalid, wfm?

There's no indication from Corey that the Utah admin has been contacted or that
the mirror has actually been fixed, so no, it should stay open until that
happens and we get it added back to our DNS.

Comment 6

[Nick Thomas [:nthomas] (UTC+12)]

This server seems to be back to normal, and is currently in the DNS record for
ftp.mozilla.org. In any case, more active monitoring of the servers is now in
place (http://nagios.mozilla.org/ftplag/)

Marking WFM since there is no specific fix to point to.

Comment 7

[Dave Miller [:justdave]]

agreed.  They were rsyncing directly from our staging server, and their
constantly being behind seems to have been a result of our slow disk array,
which is now gone since we moved to a new server with a speedy array, so they
seem to be keeping up now.

Comment 8

[Dave Miller [:justdave]]

of course, 5 minutes after I post that, nagios flags it for being out-of-date.

I'll continue to keep an eye on it...