Closed Bug 759248 Opened 14 years ago Closed 14 years ago

SCL2 and MTV1 network unreachable from Boris, mradm01; external health checks failing as well

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Atoll, Unassigned)

Details

tcptraceroute -p 22 from mradm01 and boris to adm1.scl2.svc.m.c (22/tcp), mon1.scl2.svc.m.c, and so forth. we also just got notified that scl2 has been removed from BrowserID service automatically due to health check failures
Assignee: server-ops → network-operations
Component: Server Operations → Server Operations: Netops
QA Contact: phong → ravi
Severity: critical → normal
I'm not sure if there is anything actionable for this event anymore. I cleared xlate within minutes of SRE pinging on #netops. Please close or let me know what else we can do.
slate clear confirmed to fix site issue, resolving. listed hosts known to be affected by xlate issues at https://intranet.mozilla.org/Services/Ops/FWSM and linked from Oncall page.
Group: infra
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Summary: SCL2 network unreachable from Boris, mradm01; external health checks failing as well → SCL2 and MTV1 network unreachable from Boris, mradm01; external health checks failing as well
Group: infra
This occurred again at 00:49 and recovered 5 mins later (going by nagios).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Only partially resolved I think. eg mv-moz2-linux-ix-slave04.build.mtv1 can reach buildbot-master32.srv.releng.scl3.mozilla.com:9001 (10.26.48.19) but not stage.mozilla.org 22 or 80 hg.mozilla.org 22 or 80 Both of the latter are 63.245.215 IPs.
Cleared xlates and things began to heal. We need to get off this firewall.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Looks like this is happening again. I see HOST DOWNs MTV1 from dm-nagios01 and was briefly unable to ping SCL2 host db1.iddb.scl2.svc.mozilla.com. The nagios bots in mtv1 and scl2 were knocked off too: 04:16:51 -!- nagios-mtv1 [nagios-mtv@moz-BBE3ABD.mv.mozilla.com] has quit [Ping timeout] 04:16:51 -!- nagios-svc-scl2 [nagios-svc@979AC98.5E1FE21F.D25A875A.IP] has quit [Ping timeout]
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Ashish Vijayaram [:ashish] from comment #6) > Looks like this is happening again. I see HOST DOWNs MTV1 from dm-nagios01 > and was briefly unable to ping SCL2 host db1.iddb.scl2.svc.mozilla.com. The > nagios bots in mtv1 and scl2 were knocked off too: > > 04:16:51 -!- nagios-mtv1 [nagios-mtv@moz-BBE3ABD.mv.mozilla.com] has quit > [Ping timeout] > 04:16:51 -!- nagios-svc-scl2 [nagios-svc@979AC98.5E1FE21F.D25A875A.IP] has > quit [Ping timeout] :casey says this wasn't the FWSM. Opened Bug 762857.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.