4

While asking this question, I feel that it may be dumb - but I have no idea at the moment...

How to find out the current setting for FcgidMaxProcesses on Apache?

Background

I experienced the following error: mod_fcgid: can't apply process slot for ...

My Apache2 allows MaxClients=500 and the default configuration for FcgidMaxProcesses is 1000, according to mod_fcgid docs. Therefore, the MaxProcesses should not be the limiting factor - but before starting to play around with the settings, I would prefer to check the current value. So ... how do I?

Thank you

Settings

# apache2.conf
<IfModule mpm_worker_module>
    StartServers             2
    ServerLimit             32
    MinSpareThreads         25
    MaxSpareThreads        100
    ThreadLimit             64
    ThreadsPerChild         50
    MaxClients            1000
    MaxRequestsPerChild  10000
</IfModule>

# VirtualHost configuration
<IfModule mod_fcgid.c>
    FcgidWrapper /var/www/php-fcgi-starter .php
    # Allow request up to 33 MB
    FcgidMaxRequestLen 34603008
    FcgidIOTimeout 300
    FcgidBusyTimeout 3600
</IfModule>

#/var/www/php-fcgi-starter
#!/bin/sh
export PHPRC="/etc/php5/cgi"
exec /usr/bin/php5-cgi
BurninLeo
  • 860
  • 2
  • 11
  • 28

1 Answers1

4

This is the purpose of mod_info. On the server-info page, you will see all the possible configuration options and if they are customized. If there is no custom setting, then it is the compile-time default, which does seem to be 1000 as confirmed by the documentation and source code (line 48).

Note: don't use the Location /server-info or create a link to your mod_info Location or you'll end up in Google like this server: http://dice.csail.mit.edu/server-info#mod_fcgid.c

dialt0ne
  • 3,027
  • 17
  • 27
  • 1
    mod_info is a good hint, thanks! But, as I set no configuration for the setting, this module won't tell me anything new. Is there any way to confirm the compile-time default? – BurninLeo Jul 13 '13 at 15:17
  • 1
    I added a link to source code to confirm the default. You're most likely not compiling from source - but each distribution/packager usually has source packages you extract and check if you want to be triple sure it wasn't modified during packaging. Include distribution and package version information if you want a more detailed link. – dialt0ne Jul 13 '13 at 15:35
  • 2
    Hi! Thanks for the additional tips - I think double sure is enough :) – BurninLeo Jul 14 '13 at 11:39