129.101.198.59 (mirror2.its.uidaho.edu) is part of releases.mozilla.org and is not responsive

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
critical
RESOLVED FIXED
6 years ago
3 years ago

People

(Reporter: Gavin, Assigned: ashish)

Tracking

Details

I couldn't load releases.mozilla.org earlier (request just timed out). I tried loading all of the individual mirrors behind that alias:

curl -H "Host: releases.mozilla.org" -I http://216.165.129.141
curl -H "Host: releases.mozilla.org" -I http://64.50.236.214
curl -H "Host: releases.mozilla.org" -I http://128.61.111.9
curl -H "Host: releases.mozilla.org" -I http://129.101.198.59
curl -H "Host: releases.mozilla.org" -I http://131.188.12.212
curl -H "Host: releases.mozilla.org" -I http://149.20.36.135
curl -H "Host: releases.mozilla.org" -I http://155.98.64.83
curl -H "Host: releases.mozilla.org" -I http://156.56.247.196
curl -H "Host: releases.mozilla.org" -I http://202.177.202.154
curl -H "Host: releases.mozilla.org" -I http://204.152.184.113
curl -H "Host: releases.mozilla.org" -I http://204.246.0.136

and found all of them to have reasonable response times, except for 129.101.198.59, which just times out.

I'm connecting from the Mountain View office.

Can we poke them/take them out of the pool?
Severity: major → critical
https://nagios.mozilla.org/ftplag/ knows that it's been unresponsive, and for at least a week (https://nagios.mozilla.org/ftplag/129.101.198.59-releases-weekly.png). I thought that system was set up to remove busted mirrors from the DNS pool.
It's called mirror1.its.uidaho.edu on the ftplag page, but has the same IP as mirror2.
(Assignee)

Updated

6 years ago
Assignee: server-ops → ashish
(Assignee)

Comment 3

6 years ago
129.101.198.59 has been disabled in geodns.
(Assignee)

Comment 4

6 years ago
FWIW, the mirror is still unresponsive. I'm not sure if we have the contact for the admin.

$ curl -H "Host: releases.mozilla.org" -I http://129.101.198.59
curl: (7) couldn't connect to host
It's deleted from bouncer, is there any reason to keep this bug still open?
(Assignee)

Comment 6

6 years ago
Nope.
Status: NEW → RESOLVED
Last Resolved: 6 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.