Closed
Bug 550494
Opened 14 years ago
Closed 14 years ago
planet showing two-day old content (stale git lock, maybe?)
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: reed, Assigned: oremj)
References
()
Details
http://planet.mozilla.org/ is currently showing me content from two days ago (Wednesday, 3 March 2010 :: 3:30pm). stale git lock on one or more of the webheads, maybe?
Comment 1•14 years ago
|
||
Hmm, poking around. The cron jobs have been running fine, no issues there.
Assignee: server-ops → shyam
Comment 2•14 years ago
|
||
Seems okay now, I just manually pushed the content out again. Nothing was wrong, as such. I'll try to poke around further and see if something failed. Re-open if this falls back again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
After updating "normally" all morning, it's back to showing Wednesday's content (dwitte on cookies) again :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #3) > After updating "normally" all morning, it's back to showing Wednesday's content > (dwitte on cookies) again :( This righted itself sometime this afternoon; however, right now, we're back to to showing Wednesday's content (dwitte on cookies) again :(
Reporter | ||
Updated•14 years ago
|
Assignee: shyam → server-ops
Status: REOPENED → NEW
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5) > I'm seeing contents from today. One (or more) of the webheads is likely out of sync... I'm seeing Wednesday's content here.
Comment 7•14 years ago
|
||
i manually pushed out the content again.
Status: NEW → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•14 years ago
|
||
http://planet.mozilla.org/?nocache222 is still showing the old content... Did the sync finish yet?
Reporter | ||
Comment 9•14 years ago
|
||
Still seeing old content....
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•14 years ago
|
||
just cleared NS cache.
Reporter | ||
Comment 11•14 years ago
|
||
(In reply to comment #10) > just cleared NS cache. It's not a caching problem... There has to be at least one webhead with old content. Hit each of the webheads directly using curl and see which one has old content.
Reporter | ||
Comment 13•14 years ago
|
||
This needs to be fixed now, please.
Assignee: phong → server-ops
Severity: critical → blocker
Updated•14 years ago
|
Assignee: server-ops → phong
Comment 14•14 years ago
|
||
All seven webheads are showing the current content when I hit them directly.
Comment 15•14 years ago
|
||
I'm getting current content when I hit the live site, too?
Comment 16•14 years ago
|
||
Latest I see is: March 06, 2010 Wladimir Palant — Linux New Media Award for Adblock Plus That seems right.
Comment 17•14 years ago
|
||
OK, found the problem. This content is also being served out of the new Phoenix datacenter, and the Phoenix webheads are both out-of-date and not included in the list of webheads that mradm02 knows about. Trying to figure out how
Assignee: phong → justdave
Comment 18•14 years ago
|
||
er, trying to figure out how to resolve it now, as it apparently is syncing content but there's a docroot mismatch or something.
Comment 19•14 years ago
|
||
Had this comment typed several hours ago and forgot to submit it... We apparently have problems with the way the webheads are set up in Phoenix right now. Going to take a while to figure it out, so I've removed Phoenix from the pool for this site for now. (And coincidentally www.mozilla.org as well, since they share an IP address)
Comment 20•14 years ago
|
||
Thanks for the update Dave.
Assignee | ||
Comment 21•14 years ago
|
||
Content sync -> phx has been fixed.
Comment 22•14 years ago
|
||
per comment 21.
Assignee: justdave → jeremy.orem+bugs
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•