koha-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Koha-devel] koha.org and kohadocs.org


From: Axel Bojer
Subject: Re: [Koha-devel] koha.org and kohadocs.org
Date: Fri, 21 Dec 2007 12:11:31 +0100
User-agent: Thunderbird 2.0.0.6 (X11/20071022)

Chris Nighswonger wrote:
On 12/20/07, Bünzli Daniel <address@hidden> wrote:
Le 20 déc. 07 à 17:31, Chris Nighswonger a écrit :

Next time from both locations do a traceroute from *nix teminal to
both problem sites.
Since this is happening right at the moment, here you have :

traceroute www.koha.org
(...)
11  sl-bb21-par-4-0.sprintlink.net (213.206.129.149)  31.866 ms
31.188 ms  35.398 ms
12  sl-bb24-nyc-9-0.sprintlink.net (144.232.9.166)  114.674 ms
119.987 ms  116.966 ms

There appears to be a bottleneck between hop 11 and 12 on Sprint's
network. (Not uncommon on this provider from my experience with them.)
Looks like a long-haul link from Paris to New York my guess from the
naming conventions.

traceroute www.kohadocs.org
traceroute to www.kohadocs.org (66.249.19.54), 64 hops max, 40 byte
packets
(...)
11  sl-bb21-par-4-0.sprintlink.net (213.206.129.149)  39.422 ms
39.418 ms  49.981 ms
12  sl-bb24-nyc-9-0.sprintlink.net (144.232.9.166)  190.203 ms
154.597 ms  136.152 ms

Same link is bottlenecked here as well.

but, (always so far) reachable :

traceroute git.koha.org
(...)
 5  195.186.0.126 (195.186.0.126)  21.011 ms  14.527 ms  15.446 ms
 6  i00nye-005-pos12-0.bb.ip-plus.net (138.187.159.6)  111.069 ms
112.085 ms  111.039 ms

Bottleneck between hops 5 and 6 here. Again, I'm guessing a long haul
link from Europe to New York based on the hostname of hop 6. hop 5
appears to be in Switzerland (.ch tld).
(...)
Traceroutes from both of your two different physical locations would
probably confirm issues on the same endpoints.

Just for fun I tried from Norway, and it seems to confirm your conclusion:

$ traceroute www.koha.org
traceroute to www.koha.org (66.249.19.54), 30 hops max, 40 byte packets
 1  WRT54GL (192.168.1.1)  1.365 ms  2.256 ms  2.642 ms
2 cm-84.213.189.1.getinternet.no (84.213.189.1) 9.761 ms 10.048 ms 13.043 ms 3 cm-84.208.2.125.getinternet.no (84.208.2.125) 16.478 ms 16.802 ms 17.189 ms 4 cm-84.208.26.6.getinternet.no (84.208.26.6) 13.389 ms 13.677 ms 13.918 ms
 5  64.213.76.97 (64.213.76.97)  14.191 ms  14.523 ms  16.901 ms
6 ge-6-17.car1.Amsterdam1.Level3.net (213.244.165.237) 35.261 ms 39.405 ms 26.812 ms 7 ae-32-56.ebr2.Amsterdam1.Level3.net (4.68.120.190) 27.136 ms 29.953 ms 30.384 ms 8 ae-2.ebr2.London1.Level3.net (4.69.132.133) 47.580 ms 47.265 ms 47.377 ms 9 ae-4.ebr1.NewYork1.Level3.net (4.69.132.109) 113.728 ms 114.060 ms 114.205 ms 10 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 114.429 ms ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 117.353 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 116.312 ms 11 ae-82-82.ebr2.NewYork1.Level3.net (4.69.134.89) 109.219 ms ae-92-92.ebr2.NewYork1.Level3.net (4.69.134.93) 106.452 ms ae-72-72.ebr2.NewYork1.Level3.net (4.69.134.85) 112.978 ms 12 ae-2.ebr1.Chicago1.Level3.net (4.69.132.65) 135.754 ms 136.212 ms 136.024 ms 13 ae-68.ebr3.Chicago1.Level3.net (4.69.134.58) 137.364 ms 137.124 ms 137.492 ms 14 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 156.502 ms 157.696 ms 157.928 ms 15 ae-2.ebr2.Seattle1.Level3.net (4.69.132.53) 187.413 ms 187.936 ms 187.677 ms 16 ae-23-56.car3.Seattle1.Level3.net (4.68.105.164) 190.204 ms ae-23-54.car3.Seattle1.Level3.net (4.68.105.100) 190.569 ms ae-23-52.car3.Seattle1.Level3.net (4.68.105.36) 190.618 ms 17 ge1-1.cr01.sea01.mzima.net (4.71.152.2) 196.870 ms 194.338 ms 194.568 ms 18 xe0-2.cr01.sea02.mzima.net (216.193.255.234) 192.897 ms 193.319 ms 193.043 ms 19 ge1-spry.cust.sea02.mzima.net (72.37.232.34) 192.187 ms 192.582 ms 207.110 ms
20  64.79.223.2 (64.79.223.2)  206.471 ms  207.282 ms  206.810 ms
21  vz64-015.spry.com (209.59.204.64)  209.738 ms  209.548 ms  209.186 ms
22  pippin.metavore.com (66.249.19.54)  215.616 ms  215.887 ms  195.287 ms

Everything after London1--NewYork1 is considerably slower.

Best regards
Axel bojer




reply via email to

[Prev in Thread] Current Thread [Next in Thread]