 | | | Narrowing Down A Strange Problem | Narrowing Down A Strange Problem 2004-09-15 - By Tim Burden
Hmm, note the different IP address?
I think you tracerouted the wrong host name, Samuel.
----- Original Message -----
From: "Gold, Samuel (Contractor)" <GoldS@(protected)>
To: <users@(protected)>
Cc: <ddonahue@(protected)>
Sent: Wednesday, September 15, 2004 12:26 PM
Subject: RE: [users@(protected)] Narrowing Down A Strange Problem
> I was not able to view your site and I am in Virginia.
>
> Here is my traceroute minus my host info.
> traceroute www.cyberOne.com
> traceroute: my host stuff here.
> traceroute to www.cyberOne.com (203.251.80.133), 30 hops max, 40 byte
> packets
> 1 host stuff here 0.722 ms 0.749 ms 0.463 ms
> 2 209.22.99.10 (209.22.99.10) 0.812 ms 0.909 ms 1.041 ms
> 3 209.22.99.20 (209.22.99.20) 2.345 ms 1.406 ms 3.341 ms
> 4 206.38.93.33 (206.38.93.33) 5.108 ms 2.965 ms 3.354 ms
> 5 33.250.52.1 (33.250.52.1) 22.356 ms 19.470 ms 19.197 ms
> 6 198.26.122.9 (198.26.122.9) 18.565 ms 18.825 ms 24.688 ms
> 7 198.26.122.50 (198.26.122.50) 20.241 ms 19.201 ms 21.160 ms
> 8 63.149.72.25 (63.149.72.25) 19.821 ms 19.513 ms 19.636 ms
> 9 205.171.209.77 (205.171.209.77) 18.944 ms 20.644 ms 22.846 ms
> 10 205.171.8.222 (205.171.8.222) 19.658 ms 21.841 ms 21.747 ms
> 11 205.171.251.34 (205.171.251.34) 21.535 ms 19.979 ms 27.112 ms
> 12 209.244.219.181 (209.244.219.181) 20.428 ms 22.009 ms 27.661 ms
> 13 so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13) 22.229 ms
23.164
> ms 21.219 ms
> 14 so-0-0-0.bbr1.SanJose1.Level3.net (64.159.1.133) 97.001 ms 96.782 ms
> 97.082 ms
> 15 so-14-0.hsa3.SanJose1.Level3.net (4.68.114.154) 100.608 ms 100.462
ms
> 98.983 ms
> 16 65.57.246.14 (65.57.246.14) 97.719 ms 98.150 ms 98.780 ms
> 17 211.48.63.229 (211.48.63.229) 237.281 ms 236.760 ms 238.096 ms
> 18 218.145.63.217 (218.145.63.217) 237.439 ms 235.780 ms 255.981 ms
> 19 220.73.150.129 (220.73.150.129) 316.202 ms 238.392 ms 235.265 ms
> 20 220.73.148.22 (220.73.148.22) 240.471 ms 293.412 ms 242.580 ms
> 21 203.232.42.230 (203.232.42.230) 239.512 ms 241.816 ms 239.803 ms
> 22 211.48.168.170 (211.48.168.170) 241.063 ms 239.663 ms 239.349 ms
> 23 211.224.121.250 (211.224.121.250) 242.040 ms 246.970 ms 241.131 ms
> 24 * * *
> 25 * * *
> 26 * * *
> 27 * * *
> 28 * * *
> 29 * * *
> 30 * * *
>
> -----Original Message-----
> From: David P. Donahue [mailto:ddonahue@(protected)]
> Sent: Wednesday, September 15, 2004 11:56 AM
> To: users@(protected)
> Subject: RE: [users@(protected)] Narrowing Down A Strange Problem
>
>
> So far people who can view the site are in:
> South Carolina
> North Carolina
> Missouri
> Arkansas
> And people who can not are int:
> Massachusetts
> New York
> California
>
> The only pattern I can derive from that data is the number of hops in the
> route.
>
>
> -----Original Message-----
> From: Aman Raheja [mailto:araheja@(protected)]
> Sent: Wednesday, September 15, 2004 11:53 AM
> To: users@(protected)
> Subject: Re: [users@(protected)] Narrowing Down A Strange Problem
>
>
> From how many different locations / ISPs / people you have seen this
> problem?
> I am from St Louis and am able to see the site.
> Thanks
>
> David P. Donahue wrote:
>
> >>>Did work fine for me. What is the error people get
> >>>who can't access it for whatever reason and how do
> >>>you know that there is this 1250 byte limit?
> >>>Aman Raheja
> >>>
> >>>
> >
> >No error is received for >1250b responses, it just never gets to the
> >client. I haven't narrowed it down to a specific byte size, but the
> >pattern of positive results vs. time-outs seems to hold at
> >approximately 1250 bytes. I've made a large number of GET requests and
>
> >the pattern has held. Even directory listings from Apache itself fit
> >the pattern if there are enough files in the directory to bring the
> >generated response above the 1250-ish-byte line.
> >
> >If you were able to view the site, might I ask your general location
> >and/or ISP?
> >
> >
> >David P. Donahue wrote:
> >
> >
> >
> >>Before I get into the details of my problem, let me specify that it is
> >>my belief that the Apache software (version 1.3.31) is _not_ at fault
> >>for this and I am just looking to either: 1) confirm that and look for
>
> >>solutions elsewhere; or 2) be proven wrong and hopefully solve the
> >>problem here and now.
> >>
> >>The Scenario:
> >> I have a simple website with a bunch of static files that is in place
> >>
> >>
> >
> >
> >
> >>for no other reason than to test connectivity and other issues before
> >>I
> >>
> >>
> >
> >
> >
> >>work on the new site(s). For the curious, this site is located at
> >>http://www.cyber0ne.com and, keep in mind, a lot of the functionality
> >>of the site itself is broken and it's a crappy old site from when I
> was
> >>
> >>
> >
> >
> >
> >>in college.
> >>
> >>The Symptoms:
> >> Browse to the site from the localhost (0 hops): no problems. Browse
> >>to the site from LAN hosts (1 hop): no problems. Browse to the site
> >>from hosts in the general metropolitan vecinity (few hops): no
> >>problems. Browse to the site from across the country (many hops):
> >>strange problems seen.
> >> Requests are sent to the server, noted in its logs, responded to as
> >>
> >>
> >
> >
> >
> >>usual. However, only responses (just simple GET requests for static
> >>files here) with fewer than approximately 1250 bytes are received by
> >>the client. Server logs show nothing out of the ordinary, but
> >>responses greater than approximately 1250 bytes are never received by
> >>the client and time out.
> >>
> >>The Question(s):
> >> Has anyone seen anything like this before?
> >> Can you think of _anything_ in Apache which may result in such
> >>behavior? Can you, from wherever you are, access the site? (The root
> >>index page
> >>
> >>
> >
> >
> >
> >>exceeds the 1250-ish-byte limitation so, if you can see that, you
> >>should be good.)
> >>
> >>
> >>
> >>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info. To
> unsubscribe, e-mail: users-unsubscribe@(protected)
> " from the digest: users-digest-unsubscribe@(protected)
> For additional commands, e-mail: users-help@(protected)
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info. To
> unsubscribe, e-mail: users-unsubscribe@(protected)
> " from the digest: users-digest-unsubscribe@(protected)
> For additional commands, e-mail: users-help@(protected)
>
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@(protected)
> " from the digest: users-digest-unsubscribe@(protected)
> For additional commands, e-mail: users-help@(protected)
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@(protected)
" from the digest: users-digest-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
|
