Closed Bug 333123 Opened 19 years ago Closed 19 years ago

Some FTP mirrors in releases.mozilla.org RRDNS not updating

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: morgamic, Assigned: justdave)

References

Details

User comments have come in about the FTP mirrors falling behind (by 1/2 days): 05:49 < Cameron> the news from the night is that some of the mirrors are VERY behind (like.. over a day... maybe 2 or something) I dunno what you want to do about it, but yeah I looked at this, and indeed some servers are not being updated with the new versions of extensions while some are. Could someone look into this?
Can you find me one? Or a file that hasn't updated? I just converted the test script we use on ftp.m.o to run on releases.m.o instead and it says the furthest one behind is 20 minutes.
Assignee: server-ops → justdave
http://ftp.mozilla.org/pub/mozilla.org/extensions/wizz_rss_news_reader/ vs. http://releases.mozilla.org/pub/mozilla.org/extensions/wizz_rss_news_reader/ The last two versions are not updated -- which makes it impossible to download the newest version.
Group: mozillaorgconfidential
status update: most of the world rsyncs from TDS. TDS has two boxes, and they are out-of-sync with each other. I've paged the admin at TDS, he replied to my page saying he'd be on it in about 30 minutes.
TDS mirror1 is out of disk space, TDS mirror2 is okay. ftp-rsync and releases-rsync have been moved to point at mirror2. Hopefully everyone should catch up in the next hour or so.
Anyone having any problems related to this still?
mirror2.tds is fine now, but mirror1.tds is now having problems, mirror1 has been dropped from the rsync RRDNS.
*** Bug 334420 has been marked as a duplicate of this bug. ***
*** Bug 334476 has been marked as a duplicate of this bug. ***
I think the DNS is the wrong way round. I'm seeing releases-rsync.mozilla.org pointing to 216.165.129.134 here, which is mirror1.mirrors.tds.net. Manually browsing mirror2 shows it's up to date.
I've noticed this problem with my extension (RSS Ticker). It was updated to 1.4 last night (April 17), and 12 hours later, the "not a valid install package" errors are still coming (from releases.mozilla.org), while ftp.mozilla.org has the file.
Based on comments here, I just swapped them back again, so mirror1 is live, and mirror2 is out for now. I've pinged the TDS admin again.
It's looking a lot better now. Of 12 r.m.o mirrors I checked a few minutes ago, only 1 was behind, but I've just checked now and it's up-to-date.
OK, this is resolved. The latest issues were the OSL mirror running out of disk space. We've changed the way we monitor the mirrors so we can tell if their last sync completed and not just if they started it, so we should be able to stay on top of pulling people out of the round robin when they have rsyncs that don't complete now.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.