Closed Bug 591621 Opened 15 years ago Closed 15 years ago

http://mozcom-cdn.mozilla.net/ is almost always unreachable

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pascalc, Unassigned)

Details

Our CDN is often unreachable for a few minutes, I noticed that several times today on two different machines from France. ex : http://mozcom-cdn.mozilla.net/img/tignish/template/mozilla-logo.png gives me either the image or a 'server is unreachable' message in Firefox host mozcom-cdn.mozilla.net Host mozcom-cdn.mozilla.net not found: 2(SERVFAIL) a traceroute gives me a server unreachable response most of the time. Here is a traceroute command when it works: traceroute mozcom-cdn.mozilla.net traceroute to mozcom-cdn.mozilla.net (93.184.220.20), 30 hops max, 60 byte packets 1 * * * 2 84.96.128.24 (84.96.128.24) 40.550 ms 48.115 ms 48.082 ms 3 109.129.96-84.rev.gaoland.net (84.96.129.109) 48.046 ms 48.012 ms 51.674 ms 4 * * 102.129.96-84.rev.gaoland.net (84.96.129.102) 52.201 ms 5 prs-b7-linl.telia.net (213.248.94.37) 58.919 ms V3557.brs1-sec-2.gaoland.net (84.96.244.190) 59.206 ms prs-b7-linl.telia.net (213.248.94.37) 60.222 ms 6 prs-b2-link.telia.net (213.248.87.61) 60.454 ms prs-sdix-i2-link.telia.net (80.91.253.78) 42.336 ms 37.282 ms 7 prs-sdix-i1-link.telia.net (80.91.247.149) 39.059 ms prs-sdix-i2-link.telia.net (80.91.253.78) 43.369 ms 43.914 ms 8 prs-sdix-i2-link.telia.net (80.91.248.74) 40.908 ms edgecast-ic-137708-prs-sdix-i2.c.telia.net (213.248.93.106) 46.326 ms prs-sdix-i2-link.telia.net (80.91.248.74) 48.915 ms 9 edgecast-ic-137708-prs-sdix-i2.c.telia.net (213.248.93.106) 48.562 ms 47.574 ms 93.184.220.20 (93.184.220.20) 47.214 ms
Looks like you're showing two different problems. DNS lookup failures (server not found) and server unreachable. I changed the weighting over to CDNetworks - let me know if this changes behavior.
pages are displaying correctly now, thanks
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
mrz, FWIW, I found mozcom-cdn.mozilla.net to be excruciatingly slow when I was in India. Again, my DNS lookups were taking ages to return (but eventually did) so this is probably an issue in certain parts outside the US.
That hostname resolves to either n2.panthercdn.com or wac.1237.edgecastcdn.net. It'd be useful to know which is failing.
Didn't catch that, but I can test that out the next time my dad's online.
Which is now :p shyam@airwolf:~$ time dig mozcom-cdn.mozilla.net ; <<>> DiG 9.7.0-P1 <<>> mozcom-cdn.mozilla.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8620 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;mozcom-cdn.mozilla.net. IN A ;; ANSWER SECTION: mozcom-cdn.mozilla.net. 84 IN CNAME mozcom-cdn.3crowd.mozilla.net. mozcom-cdn.3crowd.mozilla.net. 1 IN CNAME n2.panthercdn.com. n2.panthercdn.com. 12 IN A 77.67.3.157 ;; AUTHORITY SECTION: panthercdn.com. 172528 IN NS ns1.panthercdn.com. panthercdn.com. 172528 IN NS ns2.panthercdn.com. ;; Query time: 234 msec ;; SERVER: 218.248.240.181#53(218.248.240.181) ;; WHEN: Mon Aug 30 10:21:00 2010 ;; MSG SIZE rcvd: 155 Seems fast enough now. Will try to keep an eye out.
Yesterday I noticed the same problem on the European morning with css files from the cdn not being loaded (From France), one of our localizers from Spain also reported it to me, not sure if I should file a new bug since it is not reproducible.
(In reply to comment #7) > Yesterday I noticed the same problem on the European morning with css files > from the cdn not being loaded (From France), one of our localizers from Spain > also reported it to me, not sure if I should file a new bug since it is not > reproducible. A new bug is better. I'd also need a traceroute so I can figure out which cdn is having issues.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.