Closed Bug 1270337 Opened 9 years ago Closed 8 years ago

Add nagios check for upstream proxxy timeouts

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P5)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: catlee, Assigned: aselagea)

Details

Bug 1269464 was caused by proxxy regularly timing out fetching up its upstream. These showed up in papertrail with lines like this: May 4 12:57:12 proxxy1.srv.releng.use1.mozilla.com proxxy1.srv.releng.use1.mozilla.com nginx: 2016/05/04 12:57:12 [error] 101250#0: *16300531 upstream timed out (110: Connection timed out) while connecting to upstream, client: 10.134.156.231, server: queue.taskcluster.net.*, request: "GET /v1/task/epFgUuiBTMesZPJGg7eMgw/artifacts/public/build/firefox-49.0a1.en-US.linux-i686.tar.bz2 HTTP/1.1", upstream: "https://50.19.221.181:443/v1/task/epFgUuiBTMesZPJGg7eMgw/artifacts/public/build/firefox-49.0a1.en-US.linux-i686.tar.bz2", host: "queue.taskcluster.net.proxxy1.srv.releng.use1.mozilla.com" We should create a nagios alert for these kinds of messages.
Assignee: nobody → aselagea
Priority: -- → P5
proxxy won't be used with taskcluster, so this is no longer as critical.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.