Closed Bug 559986 Opened 15 years ago Closed 15 years ago

sentry failing to reach voxcdn mirror

Categories

(mozilla.org :: FTP: Mirrors, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Gavin, Assigned: reed)

Details

voxcdn is one of the primary release mirrors, and sentry currently has it marked red (down), despite it being reachable from the command line on im-sentry01. <justdave> [root@im-sentry01 ~]# curl -I http://3347-mozilla.voxcdn.com/pub/mozilla.org/ <justdave> HTTP/1.1 200 OK <justdave> [root@im-sentry01 sentry]# ./sentry.pl checknow http://3347-mozilla.voxcdn.com/pub/mozilla.org <justdave> http://3347-mozilla.voxcdn.com/pub/mozilla.org sent no response after 5 seconds! Checking recent history... <justdave> and I get that almost immediately <justdave> it doesn't wait 5 seconds <justdave> Error received: Can't connect to mozilla-mirror.3347.voxcdn.com:80 (Bad hostname 'mozilla-mirror.3347.voxcdn.com') <justdave> where's that name coming from? <gavin> that's the old one <justdave> definitely says 3347-mozilla in the config DNS at MPT can't resolve mozilla-mirror.3347.voxcdn.com, but I can - I don't know whether that's related.
and I don't know why it needs to resolve mozilla-mirror.3347.voxcdn.com, because I don't know where it's even getting that name from.
for the record, it's not in /etc/hosts
[root@im-sentry01 ~]# host 3347-mozilla.voxcdn.com 3347-mozilla.voxcdn.com is an alias for content.sjc1.site.voxcdn.net. content.sjc1.site.voxcdn.net has address 208.122.62.226 [root@im-sentry01 ~]# host 208.122.62.226 Host 226.62.122.208.in-addr.arpa. not found: 3(NXDOMAIN)
After some debugging work by justdave, figured out the problem. All resolved.
Assignee: server-ops → reed
Status: NEW → RESOLVED
Closed: 15 years ago
Component: Server Operations → FTP: Mirrors
Resolution: --- → FIXED
OK, after dumping a bunch of debug data in the app, turns out LWP::UserAgent is following redirects, and voxcdn is giving us a 301 to the nonexistent hostname. Reed fixed the config on their end, all is well.
Assignee: reed → server-ops
Component: FTP: Mirrors → Server Operations
Resolution: FIXED → INVALID
Assignee: server-ops → reed
Component: Server Operations → FTP: Mirrors
Resolution: INVALID → FIXED
You need to log in before you can comment on or make changes to this bug.