Ubuntu – mpm-prefork-module config doesn’t seem to apply

apache-2.2Ubuntu

I'm running Ubuntu 12.10 and Apache 2.4.6.

I've got

<IfModule mpm_prefork_module>
    StartServers        20
    MinSpareServers     20
    MaxSpareServers     30
    MaxClients          256
    MaxRequestsPerChild 1000
</IfModule>

In my apache2.conf file, but it doesn't seem to do anything, as even under heavy stress testing, the server only spawns up to 10 apache processes.

Any advice?

Thanks.

Best Answer

The /etc/apache2/mods-enabled/mpm_prefork.conf file's configuration of these directives is almost certainly overriding this configuration in your apache2.conf, due to the Include happening later in the apache2.conf than those directives are configured.

Change them in mpm_prefork.conf for your changes to take effect.

Related Solutions

Httpd – Running out of swap space on web servers, what to do

You're running out of swap because you're using all your RAM and then some. You have a serious problem that you need to rectify right now.

You have two choices: ignore cause and just add more RAM, or target the problem of what's actually munching on your memory.

Adding RAM is fairly cheap and fairly easy if it's your server but it's a temporary fix and if it's a VPS or a rented server, it's not so cheap. Let's have a go at fixing the root problem instead. What's sucking in that much memory? Here are a few tips:

Turn off InnoDB (unless you need it) in MySQL
Beat Apache (and MySQL) with the Stick of Configuration +5
Consider a smaller httpd like cherokee, lighttpd or nginx (they're really fast and eat almost no RAM). Main downside is you can't use .htaccess files but you can hard-code in their functionality.
Are you using an OP-code cache for PHP? Try turning it off or switching to another, more efficient one.

In terms of just getting swap items back into real RAM, you can do that by:

swapoff -a && swapon -a

But don't try then when you've got less free memory than you have things in swap. It'll crash your server.

Why are processes increasing continuously on the apache web server

This looks like you have some requests that never terminate, forcing Apache to spawn new processes until the configured maximum is reached. After that, Apache has no option to create new processes for new requests and appears dead.

It's impossible to tell what might cause this with the few data you give us.

Do you see any hints in the log files? What kind of pages to you serve to the clients? Static HTML, PHP, CGI or something else? On what OS?

Best Answer

Related Solutions

Httpd – Running out of swap space on web servers, what to do

Why are processes increasing continuously on the apache web server

Related Topic