Following the push of Firefox 3.6rc2 there are some problems with mirrorservice.org. They appear to be using a DNS round-robin, and 5 of 8 machines in that don't have (eg) /firefox/releases/3.6rc2/update/mac/he/firefox-3.6rc2.complete.mar. Don't have zh-TW win32 installer so may still be syncing. I've disabled them for now, and emailed this bug report on.
(In reply to comment #0) > Don't have zh-TW win32 installer so may still be syncing. On any of the 8 addressses in DNS I mean. That'd be the last file to sync.
Its not even as simple as then the front end machines are only really proxies their are several backed(5) copies that sync initially it usually takes several hours to pull from the master then another to sync. They all seem to be synced atm - I will chache the mirror from a six hour to four hour cycle to help things along... Phill.
Thanks for the info Phill. Did the architecture at mirrorservice change recently ? I don't recall seeing issues before.
No, been thay way for years, but when a realease happens I often have to poke thigs as the inistal rsync can take a long time. Phill.
The initial complaint here is long since fixed. For long term detection I don't think there's really much we can do on our end, that's just a danger of having multiple machines behind the same domain name. We'll just have to catch it in QA when it happens, if it continues to.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Happened today with 3.5.8, disabled right now.
One of the copies last night got marked read only due to a file system error I have removed this one from service, seem to be in sync otherwise, please reenable.
You need to log in before you can comment on or make changes to this bug.