Same Webmin/Vitualmin/Apache Version But Different Options?

Virtualmin
1

Hello

I’m running Apache/2.2.15 on 1.680/4.07.gpl on the old server and the new server. Both servers are on CentOS 6.5, but they do run different kernels. AFAIK, that’s the only difference between them.

I installed Virtualmin on the new machine then I copied over the this section from the old server to the new one.

# prefork MPM

StartServers: number of server processes to start

MinSpareServers: minimum number of server processes which are kept spare

MaxSpareServers: maximum number of server processes which are kept spare

ServerLimit: maximum value for MaxClients for the lifetime of the server

MaxClients: maximum number of server processes allowed to start

MaxRequestsPerChild: maximum number of requests a server process serves

ORIGINAL

StartServers 8

MinSpareServers 5

MaxSpareServers 20

ServerLimit 256

MaxClients 256

MaxRequestsPerChild 4000

IN USE

StartServers 2 MinSpareServers 2 MaxSpareServers 5 ServerLimit 120 MaxClients 120 MaxRequestsPerChild 4000

worker MPM

StartServers: initial number of server processes to start

MaxClients: maximum number of simultaneous client connections

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

ThreadsPerChild: constant number of worker threads in each server process

MaxRequestsPerChild: maximum number of requests a server process serves

NOT IN USE

StartServers 4 MaxClients 300 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0

BUT
the new server shows this config: http://i.imgur.com/hxxWfk7.png
the old server shows this config: http://i.imgur.com/fZm7iKx.png

Why the difference in options from one Apache to the other?

2

Howdy,

Well, the options being set appear to be the same, they’re just in a different order.

I’m not sure why they’re in a different order, but that shouldn’t be a problem of any sort.

I also see that there’s one additional option available on your new server – that may be due to an Apache module that’s enabled on your new server but not your old one.

-Eric

3

The only module the old server has that the new one doesn’t is the Cloudflare module. The new one has a lot more modules, since I had disabled some to save memory. If you would like to take a look at the diff here it is (unique values to either column are highlighted): https://drive.google.com/file/d/0B8M2G_l-f_g6eGszVUU3SG1UUFE/edit?usp=sharing

Thanks Eric!

4

Howdy,

The new server is the one that has the extra option, correct? The one labeled “Display extended status information”?

I suspect the additional option is related to one of those additional modules that’s enabled, perhaps mod_status.

-Eric