Georgi Chorbadzhiyski wrote:
> Chirouze Olivier wrote:
>> I'm adding information to my own message... Hope someone will hear me!
>>
>> I spent the day trying to test how the status page worked. I even had my
>> first look at the source code.
>> Apparently, m
ter to
/server-status
and you'll get the request info always.
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/us
on. It looks like the apache module after
> writing to STDIN of this program doesn't wait for
>
> newline termination output from program (which it should so as per
> specification), but immediately reads whatever is on pipe
>
> which is nothing for first execution
592 0.0
> 0.020.98? ?
> ..reading..
DoS attack, slashdot effect, mod_proxy serving requests to slow clients?
Try http://host/server-status?notable to see IPs, vhost and requests instead of
...reading... text.
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
-
ed
> CustomLog /cob/cob-access-log-%Y-%m-%d.log combined
>
>
>
> RotateLogs On
> RotateLogsLocalTime On
> RotateInterval 86400
>
Well, this instructs the module to rotate logs once per day. If you start the
server
at 5 AM, everyday at 5 AM logs will
gt;> This allows 1 request per 20 seconds from IP.
>
> Yes, but this restricts via IP and it can be occured, that more
> clients use the same IP as a gateway.
Sure, but isn't this what you actually want - "accept maximum 20 requests
from an apache client in a second". Ho
sible to
make such configuration. May be there is some bug in cronolog. I've
used cronolog on some pretty heave loaded sites and never saw such a
problem like yours.
Can you try rotatelogs program from apache distribution and see if the
problem persists.
--
Ge
file.
Basically apache just opens the log program and writes requests to it
no synchronization takes place. Make sure every cronolog instance writes
to it's own file.
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
-
mit 1/minute --hashlimit-burst 1 --hashlimit-htable-expire 2
--hashlimit-htable-gcinterval 1000 -j ACCEPT
This allows 1 request per 20 seconds from IP.
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
-
The official User-To-U
ld just
dies without logging the transfer.
Is there a way to stop apache child serving request but without loosing log
information?
Graceful doesn't work for me, because I want to stop the transfer and graceful
is just advisory.
Tested on Linux 2.6.17.7/Slamd64 and Linux 2.4.32/Slackware 11.
10 matches
Mail list logo
