Both sites are routinely unavailable from this part of the world (europe). This is quite annoying (git.koha.org is, however, always up). Best, Daniel
Bünzli Daniel <daniel.buenzli@erratique.ch> wrote:
Both sites are routinely unavailable from this part of the world (europe). This is quite annoying (git.koha.org is, however, always up).
I've not noticed that from this part of the world (Europe). Have you noticed any pattern to it and tried checking from a different network connection when you think it's down, to eliminate local problems? Regards, -- MJ Ray http://mjr.towers.org.uk/email.html tel:+44-844-4437-237 - Webmaster-developer, statistician, sysadmin, online shop builder, consumer and workers co-operative member http://www.ttllp.co.uk/ - Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
Le 20 déc. 07 à 14:23, MJ Ray a écrit :
Have you noticed any pattern to it and tried checking from a different network connection when you think it's down, to eliminate local problems?
This happens from two separate physical locations (although it may be the same provider). Couldn't infer any pattern. Le 20 déc. 07 à 14:26, Mason James a écrit :
if you have trouble access these sites in your area of the world, try the 'coralised' cache of these sites
Thanks I'll try that next time. Daniel
On 12/20/07, Bünzli Daniel <daniel.buenzli@erratique.ch> wrote:
Le 20 déc. 07 à 14:23, MJ Ray a écrit :
Have you noticed any pattern to it and tried checking from a different network connection when you think it's down, to eliminate local problems?
This happens from two separate physical locations (although it may be the same provider). Couldn't infer any pattern.
Le 20 déc. 07 à 14:26, Mason James a écrit :
if you have trouble access these sites in your area of the world, try the 'coralised' cache of these sites
Thanks I'll try that next time.
Next time from both locations do a traceroute from *nix teminal to both problem sites. This *should* turn up any guilty parties. ie. gateway issues, router outages, overloads, site outages, etc. -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org
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 traceroute to www.koha.org (66.249.19.54), 64 hops max, 40 byte packets 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 16.947 ms 20.818 ms 17.320 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 26.200 ms 19.811 ms 18.686 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 15.428 ms 21.826 ms 23.696 ms 5 195.186.0.126 (195.186.0.126) 17.993 ms 18.317 ms 24.928 ms 6 i79zhb-015-vla200.bb.ip-plus.net (138.187.129.62) 22.771 ms 21.917 ms 18.081 ms 7 i79tix-025-xxx1-1.bb.ip-plus.net (138.187.129.82) 15.307 ms 19.798 ms 17.700 ms 8 sl-gw10-zur-5-0-1.sprintlink.net (80.93.9.125) 21.013 ms 14.940 ms 25.695 ms 9 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 26.198 ms 15.977 ms 21.069 ms 10 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 21.379 ms 22.794 ms 26.077 ms 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 13 sl-bb21-nyc-6-0.sprintlink.net (144.232.13.186) 129.123 ms 116.106 ms 122.742 ms 14 sl-bb25-nyc-11-0.sprintlink.net (144.232.13.1) 113.911 ms 114.653 ms 109.481 ms 15 sl-bb24-chi-2-0.sprintlink.net (144.232.9.156) 136.498 ms 144.039 ms 153.779 ms 16 sl-bb20-che-2-0.sprintlink.net (144.232.20.161) 168.593 ms 295.205 ms 216.897 ms 17 sl-bb21-che-15-0.sprintlink.net (144.232.15.142) 152.146 ms 158.933 ms 161.073 ms 18 sl-crs2-stk-0-4-0-3.sprintlink.net (144.232.20.141) 178.397 ms 177.328 ms 178.348 ms 19 * sl-bb23-sj-10-0.sprintlink.net (144.232.20.113) 183.217 ms 184.682 ms 20 sl-crs2-ana-0-4-0-2.sprintlink.net (144.232.18.56) 189.311 ms 197.134 ms 181.504 ms 21 sl-bb21-ana-15-0.sprintlink.net (144.232.1.60) 204.115 ms 190.019 ms * 22 sl-gw28-ana-0-0.sprintlink.net (144.232.1.30) 188.714 ms 193.081 ms 220.385 ms 23 sl-inetconn-138746-0.sprintlink.net (160.81.147.90) 196.346 ms 217.812 ms 207.232 ms 24 66.192.249.99 (66.192.249.99) 212.532 ms 214.548 ms 221.568 ms 25 * * * 26 * * *
etc.
traceroute www.kohadocs.org traceroute to www.kohadocs.org (66.249.19.54), 64 hops max, 40 byte packets 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 21.717 ms 14.797 ms 16.971 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 22.746 ms 17.641 ms 19.881 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 16.482 ms 24.118 ms 23.033 ms 5 195.186.0.126 (195.186.0.126) 30.118 ms 17.598 ms 26.106 ms 6 i79zhb-015-vla200.bb.ip-plus.net (138.187.129.62) 25.305 ms 18.867 ms 22.044 ms 7 i79tix-025-xxx1-1.bb.ip-plus.net (138.187.129.82) 16.521 ms 38.712 ms 16.316 ms 8 sl-gw10-zur-5-0-1.sprintlink.net (80.93.9.125) 20.904 ms 37.214 ms 18.249 ms 9 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 27.121 ms 17.717 ms 19.475 ms 10 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 26.492 ms 21.837 ms 24.078 ms 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 13 sl-bb21-nyc-6-0.sprintlink.net (144.232.13.186) 148.460 ms 207.556 ms 121.656 ms 14 sl-bb25-nyc-11-0.sprintlink.net (144.232.13.1) 126.771 ms 111.662 ms 117.068 ms 15 sl-bb24-chi-2-0.sprintlink.net (144.232.9.156) 141.993 ms 261.778 ms 185.009 ms 16 sl-bb20-che-2-0.sprintlink.net (144.232.20.161) 162.863 ms 158.728 ms 172.837 ms 17 sl-bb21-che-15-0.sprintlink.net (144.232.15.142) 160.552 ms 163.599 ms 152.671 ms 18 sl-crs2-stk-0-4-0-3.sprintlink.net (144.232.20.141) 182.922 ms 178.888 ms 300.423 ms 19 sl-bb23-sj-10-0.sprintlink.net (144.232.20.113) 179.177 ms 182.155 ms 193.855 ms 20 sl-crs2-ana-0-4-0-2.sprintlink.net (144.232.18.56) 185.169 ms 200.895 ms 183.113 ms 21 sl-bb21-ana-15-0.sprintlink.net (144.232.1.60) 188.717 ms 190.589 ms 190.342 ms 22 sl-gw28-ana-0-0.sprintlink.net (144.232.1.30) 185.361 ms 199.765 ms 185.087 ms 23 sl-inetconn-138746-0.sprintlink.net (160.81.147.90) 194.865 ms 207.669 ms 201.588 ms 24 66.192.249.99 (66.192.249.99) 214.779 ms 219.106 ms 220.868 ms 25 * * * 26 * * * 27 * * *
etc. but, (always so far) reachable :
traceroute git.koha.org traceroute to git.koha.org (64.79.208.60), 64 hops max, 40 byte packets 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 15.283 ms 14.775 ms 15.158 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 16.576 ms 13.775 ms 15.185 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 15.237 ms 15.936 ms 15.530 ms 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 7 i00eqx-005-pos5-0.bb.ip-plus.net (138.187.159.38) 114.584 ms 114.446 ms 114.694 ms 8 eqix-peer.iad01.mzima.net (206.223.115.62) 126.521 ms 115.755 ms 126.413 ms 9 eos2-25.cr01.lax02.mzima.net (216.193.255.129) 188.661 ms 189.451 ms 196.935 ms 10 eos1-21.cr02.sjc02.mzima.net (216.193.255.73) 188.592 ms eos1-20.cr02.sjc02.mzima.net (216.193.255.161) 203.596 ms eos1-21.cr02.sjc02.mzima.net (216.193.255.73) 199.835 ms 11 eos1-22.cr01.sea01.mzima.net (216.193.255.170) 208.407 ms 218.617 ms eos1-23.cr01.sea01.mzima.net (216.193.255.174) 209.853 ms 12 xe0-2.cr01.sea02.mzima.net (216.193.255.234) 208.511 ms 217.958 ms 215.096 ms 13 ge1-spry.cust.sea02.mzima.net (72.37.232.34) 208.317 ms 207.638 ms 206.807 ms 14 64.79.223.2 (64.79.223.2) 210.734 ms 209.754 ms 210.842 ms 15 vz64-002.spry.com (209.59.204.38) 208.975 ms 207.688 ms 208.776 ms 16 gimli.metavore.com (64.79.208.60) 208.433 ms 207.933 ms 206.965 ms
Best, Daniel
On 12/20/07, Bünzli Daniel <daniel.buenzli@erratique.ch> 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 traceroute to www.koha.org (66.249.19.54), 64 hops max, 40 byte packets 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 16.947 ms 20.818 ms 17.320 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 26.200 ms 19.811 ms 18.686 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 15.428 ms 21.826 ms 23.696 ms 5 195.186.0.126 (195.186.0.126) 17.993 ms 18.317 ms 24.928 ms 6 i79zhb-015-vla200.bb.ip-plus.net (138.187.129.62) 22.771 ms 21.917 ms 18.081 ms 7 i79tix-025-xxx1-1.bb.ip-plus.net (138.187.129.82) 15.307 ms 19.798 ms 17.700 ms 8 sl-gw10-zur-5-0-1.sprintlink.net (80.93.9.125) 21.013 ms 14.940 ms 25.695 ms 9 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 26.198 ms 15.977 ms 21.069 ms 10 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 21.379 ms 22.794 ms 26.077 ms 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 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 21.717 ms 14.797 ms 16.971 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 22.746 ms 17.641 ms 19.881 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 16.482 ms 24.118 ms 23.033 ms 5 195.186.0.126 (195.186.0.126) 30.118 ms 17.598 ms 26.106 ms 6 i79zhb-015-vla200.bb.ip-plus.net (138.187.129.62) 25.305 ms 18.867 ms 22.044 ms 7 i79tix-025-xxx1-1.bb.ip-plus.net (138.187.129.82) 16.521 ms 38.712 ms 16.316 ms 8 sl-gw10-zur-5-0-1.sprintlink.net (80.93.9.125) 20.904 ms 37.214 ms 18.249 ms 9 sl-bb20-zur-13-0.sprintlink.net (80.93.8.37) 27.121 ms 17.717 ms 19.475 ms 10 sl-bb20-fra-11-1.sprintlink.net (213.206.129.155) 26.492 ms 21.837 ms 24.078 ms 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 traceroute to git.koha.org (64.79.208.60), 64 hops max, 40 byte packets 1 * * * 2 1-48.2-85.cust.bluewin.ch (85.2.48.1) 15.283 ms 14.775 ms 15.158 ms 3 net481.bwrt2zhb.bluewin.ch (195.186.121.1) 16.576 ms 13.775 ms 15.185 ms 4 po20.bwrt2inb.bluewin.ch (195.186.0.101) 15.237 ms 15.936 ms 15.530 ms 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).
16 gimli.metavore.com (64.79.208.60) 208.433 ms 207.933 ms 206.965 ms
Notice here, the server hosting koha git did respond. However, with RTT's like these there is a good chance some of the packets TTL's are expiring before they reach one end or the other. The server hosting the two websites may be behind a firewall or the gateway may be setup to drop ICMP packets thus there is no final response in the traceroutes for those sites. Not much you or koha can do abou this. Probably the State side routers are overloaded. Sprint has a bad habit of doing this in my experience. There may also be TCP window scaling misconfigurations between the endpoints on the trans-atlantic links which will cause these kinds of issues as well. Traceroutes from both of your two different physical locations would probably confirm issues on the same endpoints. Kind regards, -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org
Chris Nighswonger wrote:
On 12/20/07, Bünzli Daniel <daniel.buenzli@erratique.ch> 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
On 12/21/07, Axel Bojer <axelb@skolelinux.no> wrote:
Chris Nighswonger wrote:
On 12/20/07, Bünzli Daniel <daniel.buenzli@erratique.ch> 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 Everything after London1--NewYork1 is considerably slower.
A major factor here is also the time of day and year. Check out these traffic graphs for AMS-IX, probably the largest internet backbone maintainer in the world: http://www.ams-ix.net/technical/stats/ -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org
On 2007/12/21, at 2:00 AM, Bünzli Daniel wrote:
Both sites are routinely unavailable from this part of the world (europe). This is quite annoying (git.koha.org is, however, always up). Best,
hi Daniel if you have trouble access these sites in your area of the world, try the 'coralised' cache of these sites like this... http://www.koha.org.nyud.net/ http://www.kohadocs.org.nyud.net/ some more info is here http://www.coralcdn.org/ or try the google's cached copy too :) Cheers, Mason.
participants (5)
-
Axel Bojer -
Bünzli Daniel -
Chris Nighswonger -
Mason James -
MJ Ray