Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Apache httpd process consumes all memory right after start |
|
Author |
|
duir
Joined: 16 May 2008 Posts: 2 Location: Prague
|
Posted: Fri 16 May '08 21:28 Post subject: Apache httpd process consumes all memory right after start |
|
|
Hello,
I have a very weird problem that I've been playing with over the last few days but failed to figure it out.
Symptoms:
- Immediately after the Apache service is started, two httpd processes are created and one of them (the child apparently) keeps on consuming all available memory until it causes the workstation to seize any operation
- The error logs gets tons of identical messages like: "[error] (OS 10022)An invalid argu
ment was supplied. : Child 3408: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive."
Environment:
- Notebook DELL Latitude D630, 2 CPUs, 3 GB RAM
- Apache (latest stable) version Apache/2.2.8 (Win32)
- MS Windows XP Professional SP 3
- AVG 7.5 Anti-Virus Network Edition
- (Windows Firewall not running)
Solution attempts:
- Using only a single CPU (BiOS switch) = no effect
- Installing older versions of Apache including the 1.x line = same behaviour
- Listening at port 8080 instead of the default 80 = no effect
- Adding the Win32DisableAcceptEx directive to httpd.conf = now the behaviour differs:
o the httpd child process stays at moderate cca 6.5 MB memory
o the error.log contains no error messages (and says that "Disabled use of AcceptEx() WinSock2 API")
o but when I try to look at http://localhost the browser keeps loading until it says that the page is not available
o similar behaviour is when I try communicating raw HTTP instructions over "telnet localhost 80" - it says that we're connected, but then never answers a GET request
I would be very grateful for about any idea what to do.
Thanks
Duir[/u] |
|
Back to top |
|
James Blond Moderator
Joined: 19 Jan 2006 Posts: 7371 Location: Germany, Next to Hamburg
|
Posted: Mon 26 May '08 14:03 Post subject: |
|
|
try adding Win32DisableAcceptEx to your httpd.conf and restart |
|
Back to top |
|
duir
Joined: 16 May 2008 Posts: 2 Location: Prague
|
Posted: Mon 26 May '08 14:37 Post subject: |
|
|
Thank you for your answer, but look at the "Solution attempts", where I describe the effects of this.
Thanks
Duir |
|
Back to top |
|
|
|
|
|
|