Closed Bug 1317786 Opened 8 years ago Closed 8 years ago

[Air Mozilla] Unable to connect to Chief

Categories

(Infrastructure & Operations :: IT-Managed Tools, task)

Product:
Infrastructure & Operations
Component:
IT-Managed Tools
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: peterbe, Assigned: ericz)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3728])

I can't connect to Chief to deploy Air Mozilla stage or prod. Also, as of today, it seems dev failed to upgrade. It usually auto-deploys 5 min after I push a commit to github.com/mozilla/airmozilla master. https://whatsdeployed.io/s-6pt When I try to go to http://genericadm.private.phx1.mozilla.com/chief/air.dev it says it's unable to connect even though I am connected to the VPN. I have an urgent fix I need to deploy to stage and prod.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/3728]
Assignee: server-ops-webops → eziegenhorn
Chief is now available again. Apache was not running was the immediate cause, trying to figure out why if possible.
This was me. I rebooted this host for kernel updates and puppet hadn't run to kick the process into action again. sorry about that!
We've made Apache turn on at boot now on this host and also we're modifying our patching automation to force a puppet run which will catch things like this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
I'm in! Yay! Thanks
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.