Closed Bug 632299 Opened 13 years ago Closed 13 years ago

When no nodes are available to service SUMO, redirect to hardhat

Categories

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

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: cshields, Assigned: oremj)

References

Details

During today's SUMO outage when no nodes were available to zeus, users got a blank page and 500 error. We should redirect to hardhat should this happen again.

(be sure this gets implemented in SJC and PHX please)
Just to flex my knowledge but not actually do it,

Virtual Servers | support.mozilla.com-ssl | Connection Management | Connection Error Settings | error_file

It's already set to outage.html.  

[root@zlb01 extra]# cat outage.html 
<meta http-equiv="refresh" content="0;url=http://hardhat.mozilla.net/en-US/outages.html"/>

hardhat.mozilla.net is hosted at bitgravity and apparently offline?
Looks like they are back online. RESOLVED?
Yeah, this was a bitgravity problem that happened to coincide with the SUMO outage.  Unfortunate coincidence, nothing for us to do here.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.