getfirebug.com is broken, no content is rendered

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
major
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: limi, Assigned: fox2mike)

Tracking

Details

(URL)

Navigation etc is rendered, but not the content.

Examples:
http://getfirebug.com/downloads
http://getfirebug.com/whatisfirebug

In the source, you can find things like:

<title><!-- Undefined content: article_headline --> : Firebug</title>

<!-- Undefined content: article_body -->
(Assignee)

Comment 1

8 years ago
Hey guys,

Did you change/remove content off the site? I'm getting 404s for a large number of URLs, including /blog...for example. Wondering if there were changes done that got automatically picked up and pushed out?
No, I have not changed anything.

Comment 3

8 years ago
I haven't touched anything since the launch. I'll talk a look when I get into the office today.

Comment 4

8 years ago
Looks like something is broken with the CMS getfirebug.com uses (Perch) - I can't log into the control panel at https://getfirebug.com/perch/ - I get redirected back to the log in page, and nothing happens.

My guess is we're being affected by bug 537778 again, which doesn't make a lot of sense if nothing changed on the server. But the symptoms are the same.

fox2mike - I can send you the admin log in - ping me on IRC.
Severity: normal → major
OS: Mac OS X → All
Hardware: x86 → All
(Assignee)

Updated

8 years ago
Assignee: server-ops → shyam
(Assignee)

Comment 5

8 years ago
With help from Neil, this seems to a perch randomly deciding to wipe out data from the DB issue.

I've restored a dump of getfirebug_com_perch from the 22nd and the site seems to be okay now. Neil is manually fixing stuff that isn't in that dump.
(Assignee)

Comment 6

8 years ago
Calling this done from IT's side. I'll be happy to know what the issue was though that cause perch to misbehave.
Status: NEW → RESOLVED
Last Resolved: 8 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.