View Single Post
  #2  
Old 29th October 2012, 17:07
cbj4074 cbj4074 is offline
Senior Member
 
Join Date: Nov 2010
Posts: 392
Thanks: 29
Thanked 58 Times in 50 Posts
Default

It seems that pasting the following directive into the site's "Apache Directives" box resolves the issue:

Code:
<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 5000
</IfModule>
The directive value, 5000, is equal to the value that is defined in System -> Server Config -> example.com -> FastCGI [tab] -> FastCGI max. Requests.

Given that this problem emerges in a default ISPConfig installation, my humble opinion is that this should be fixed in ISPConfig. That is to say, ISPConfig should automatically add "FcgidMaxRequestsPerProcess 5000" to each site's virtual host configuration (where 5000 is the value defined for "FcgidMaxRequests", via the interface):

Code:
<IfModule mod_fcgid.c>
        FcgidIdleTimeout 300
        FcgidProcessLifeTime 3600
        # FcgidMaxProcesses 1000
        FcgidMaxRequestsPerProcess 5000
        FcgidMinProcessesPerClass 0
        FcgidMaxProcessesPerClass 100
        FcgidConnectTimeout 3
        FcgidIOTimeout 360
        FcgidBusyTimeout 300
        FcgidMaxRequestLen 1073741824
</IfModule>
Better yet would be to add another field, "FastCGI max. Requests per Process", to the FastCGI configuration interface, so that this value may be controlled independently of "FcgidMaxRequestsPerProcess".

I have added a thorough explanation of this problem to the relevant ServerFault question at http://serverfault.com/a/442768/142864 .
Reply With Quote