I'm encountering issues on a dedicated Ubuntu 12.04 LTS (Apache/2.2.22), PHP 5.3 with APC.
Every few hours I see this happen:
[Fri Aug 17 15:36:51 2012] [error] server reached MaxClients setting, consider raising the MaxClients setting
This causes the server to drop/refuse all connections.
I'm part way through setting up a Railo server, running alongside Apache on a Ubuntu Rackpspace cloud server.
I've got Apache working fine, it will server PHP pages, I've got subdomains set up as well, that's all fine.
I am trying to load test an amazon centos instance sitting behind the amazon loadbalancer.
The application is written on php and uses the elastic cache and media is stored in s3 bucket.
When the server gets more than 1000 concurrent requests its starts giving "Apache interanl dummy connection" and the pages dont load when tried externally, even though the load uptime metric does not go beyond 1.
I have a question. Over time, should an apache process's memory consumption grow? I am wondering if this is normal apache behavior or we may be causing this somehow in code?
Basically, we have a simple LAMP stack running Drupal. On an apache restart the processes fire up @ 120MB and eventually all the processes climb to 500-1GB of memory(resident aka physical-non-swap).
I have an Apache server that is serving a django application with mod_wsgi. I'm wondering if there is a simple way to throttle requests at the apache level based on the machine's load.
Ideally I want an apache module that if the load is below a certain figure, everything works OK. However if the load is above something, then X% of IP addresses will be served the static html page for Y minutes.
I'm using mod-rpaf with Apache 2.4 and it's working properly (showing the real client IP's) in my Apache access_log... but not in my error_log.
I'm trying to optimize our web servers to handle as much connections as possible. I read a many posts and the Apache notes. I'm trying to understand which value should I choose for MaxRequestsPerChild.
At first, I've tried setting it to 4,000, but the server had difficulties handling many request, so I've started raising it.
If you have like... 10 cores... and you use Apache and your load average is always under 5.0...
Would it slow your site any if you lowered to 6 cores?
(assuming you never reached any spikes that hit 6.0 in load)
Specs:
Xen, 10 Cores at 2.0GHz, CentOS 5 64bit, using "uptime" to find load averages.
I had WAMP running with PHP 5.2. PHP errors where written to it's own log file.
I then swapped to PHP 5.3 and the errors where written to the Apache log.