Apache stop working sometimes.

ThreadsPerChild setting

[Kaboo]

Hi, this happened 2 times:
My server was running Apache,
and without any advise nobody, including me on the server machine can access my site,phpmyadmin,etc.
Apache doesn't crash when this happen, it still running, but without working.

I restarted apache and the server but it doesn't worked.
Here's the error log:

[Mon Jan 04 13:25:19 2010] [notice] Digest: generating secret for digest authentication ...
[Mon Jan 04 13:25:19 2010] [notice] Digest: done
[Mon Jan 04 13:25:20 2010] [notice] Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Mon Jan 04 13:25:20 2010] [notice] Server built: Jul 22 2009 11:35:54
[Mon Jan 04 13:25:20 2010] [notice] Parent: Created child process 2864
[Mon Jan 04 13:25:21 2010] [notice] Digest: generating secret for digest authentication ...
[Mon Jan 04 13:25:21 2010] [notice] Digest: done
[Mon Jan 04 13:25:22 2010] [notice] Child 2864: Child process is running
[Mon Jan 04 13:25:22 2010] [notice] Child 2864: Acquired the start mutex.
[Mon Jan 04 13:25:22 2010] [notice] Child 2864: Starting 150 worker threads.
[Mon Jan 04 13:25:22 2010] [notice] Child 2864: Starting thread to listen on port 443.
[Mon Jan 04 13:25:22 2010] [notice] Child 2864: Starting thread to listen on port 80.
[Mon Jan 04 13:25:22 2010] [warn] Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting

There's no ThreadsPerChild in xampp/apache/conf/httpd.conf, may i change it on some file?
I also tried to unistall apache service but it doesn't worked.

PS.: I use Windows Server 2003, 4GB Ram, and i use Apache 2.2
I think i must change ThreadsPerChild setting... but since it's not on httpd.conf, where it is?
Thanks.

[Kaboo]

I discovered the problem, i was being attacked.
The guy attacks my Apache, lots of requests(1920 maximum) and BAM!.. site offline :( .
I installed mod_evasive on apache but i still can be attacked by someone... there was no ip in /server-status.

Any ideas?

Thanks.

[jdMorgan]

If you have a firewall or a router with some firewall capability, then block his IP address, IP address range, or even his whole ISP at that level. Once he gives up, you can relax or remove the 'filter'.

Jim