ween the web server and the end user.
> Somehow the closing of the socket/connection by the browser is not
> picked up by the web server. And somehow the browser issues lots of
> requests.
> I have not completely ruled out that it might be a Apache web server bug
> as well.
>
e558c4) at main.c:638
Sander Temme-2 wrote:
>
>
> On Nov 7, 2007, at 9:31 AM, Andrew Rosolino wrote:
>
>> I restarted apache and all was fine.. but then 20 minutes later
>> they went
>> back all into a reading state.. it appears as if slowly each
>> pro
I saved the file with the full output do you want to see that.. i only took a
section from it.
Christian Folini-4 wrote:
>
> On Thu, Nov 08, 2007 at 10:27:59AM -0800, Andrew Rosolino wrote:
>>
>> Ok I did it but how am I suppose to read this?
>
> That's not the i
ffic, then it would not tell you much.
>
> regs,
>
> Christian
>
> On Wed, Nov 07, 2007 at 09:31:58AM -0800, Andrew Rosolino wrote:
>>
>> Hi this keeps happening a lot where my server will be unresponsive... it
>> just
>> hangs forever.. so I checked th
But I am not sure
> they are in the forensic log as your status suggests
> they are still being read.
>
> tcpdump outside of your apache could help here (start
> with "tcpdump -A -s 0 port xxx" here. Unless it is
> https traffic, then it would not tell you much.
>
&
Hi this keeps happening a lot where my server will be unresponsive... it just
hangs forever.. so I checked the apache server-status and there was 131
requests that looked like this..
39-16 2177 0/67/114 R 0.95 47 562 0.0 0.48 0.66 ? ? ..reading..
40-16 29189 0/220/220 R 3.40 47 135 0.0 0.67
