Closed Bug 408058 Opened 18 years ago Closed 18 years ago

AUS boxes slow to pick up new snippets

Categories

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

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Unassigned)

References

()

Details

Tb1.5.0.14 RC1 was pushed onto the betatest channel at 03:30 PST, but not all the machines behind aus2.m.o are serving the data. Polling the URL typically gives about 25 out of every 50 requests that returning the null update. At the same time, nightly updates seem to be working fine, as are those for older release versions. While trouble shooting this on IRC, Dave has tried restarting Apache on all the webheads, and we've confirmed that throttling is not enabled.
Questions: * anything preventing boxes from viewing these files (permissions, firewall, etc.)? * any changes happen tues night that could affect this stuff? * none of this is involving .nl somehow? * something with the byte-code cache or NS cache? If this fixes itself over time, it's likely the NS or PHP byte-code cache messing things up.
Dave also checked the NS rules for AUS. cf pasted the headers he was getting in his tests showing no "Via:" header from the NS.
This is working now. Were any changes made ?
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
The problem has happened again for Firefox 3.0b2 snippets, which were pushed live at 11:30 PST. Can we get someone to look into this ?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Summary: Only half of AUS boxes serving Tb1.5.0.14 on betatest → AUS boxes slow to pick up new snippets
From offline discussion with morgamic, he didnt change anything to make AUS start working for the TB1.5.0.14 bits. We're now hitting same problem on AUS with FF3.0beta2 updates, but when we look on AUS, we see the files there.
One example is: file: /opt/aus2/incoming/3/Firefox/3.0b1/Linux_x86-gcc3/2007110903/be/betatest/complete.txt url: https://aus2.mozilla.org/update/1/Firefox/3.0b1/2007110903/Linux_x86-gcc4/be/betatest/update.xml
gcc4 != gcc3 here, so that's why it can't find the update.
(In reply to comment #7) > gcc4 != gcc3 here, so that's why it can't find the update. > For example: https://aus2.mozilla.org/update/1/Firefox/3.0b1/2007110903/Linux_x86-gcc3/be/betatest/update.xml ...works, but: https://aus2.mozilla.org/update/1/Firefox/3.0b1/2007110903/Linux_x86-gcc4/be/betatest/update.xml ...does not work. We think using "gcc4" for the locales is related to a recent build update, so are redoing our updates. Sorry for the noise.
Status: REOPENED → RESOLVED
Closed: 18 years ago18 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.