Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: fcgid 2.3.5 FcgidProcessLifeTime no effect |
|
| Author |
|
pauliu
Joined: 14 Mar 2010
Posts: 2
|
 Posted: Sun 14 Mar '10 11:58 Post subject: fcgid 2.3.5 FcgidProcessLifeTime no effect |
 |
|
After updated from 2.2b to 2.3.5, seems the idle processes do not exit after reached the FcgidProcessLifeTime. Go back to 2.2b again is no such problem.
Very much appreciate for any help. Thanks.
The server is Apache 2.2.15 running on Win XP.
My fcgid settings
LoadModule fcgid_module modules/mod_fcgid.so
FcgidIdleTimeout 120
FcgidIdleScanInterval 60
FcgidBusyTimeout 120
FcgidBusyScanInterval 60
FcgidProcessLifeTime 300
FcgidMinProcessesPerClass 3
FcgidMaxProcesses 48
FcgidMaxProcessesPerClass 24
FcgidMaxRequestsPerProcess 500
FcgidConnectTimeout 8
FcgidIOTimeout 60
FcgidInitialEnv PHPRC "c:/php5/"
FcgidInitialEnv PATH "c:/php5;C:/WINDOWS/system32;C:/WINDOWS;C:/WINDOWS/System32/Wbem;"
FcgidInitialEnv SystemRoot "C:/Windows"
FcgidInitialEnv SystemDrive "C:"
FcgidInitialEnv TEMP "C:/WINDOWS/TEMP"
FcgidInitialEnv TMP "C:/WINDOWS/TEMP"
FcgidInitialEnv windir "C:/WINDOWS"
AddHandler fcgid-script .php
AddHandler fcgid-script .php3 |
|
| Back to top |
|
glsmith
Moderator
Joined: 16 Oct 2007
Posts: 2268
Location: Sun Diego, USA
|
| Posted: Sun 14 Mar '10 20:05 Post subject: |
|
|
Reading the docs on that directive I see a caveat which states
"... will be terminated, if the number of processses for the class exceeds FcgidMinProcessesPerClass."
You have a MinProcessPerClass of 3, so if it never reaches 4 processes for that class, this setting will not have effect. That is how I read it anyway. |
|
| Back to top |
|
pauliu
Joined: 14 Mar 2010
Posts: 2
|
| Posted: Mon 15 Mar '10 3:48 Post subject: |
|
|
| glsmith wrote: | Reading the docs on that directive I see a caveat which states
"... will be terminated, if the number of processses for the class exceeds FcgidMinProcessesPerClass."
You have a MinProcessPerClass of 3, so if it never reaches 4 processes for that class, this setting will not have effect. That is how I read it anyway. |
It goes up to my max. limit at 24 processes and never decrease even some processes are idle for a long time. |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7404
Location: EU, Germany, Next to Hamburg
|
| Posted: Mon 15 Mar '10 14:14 Post subject: |
|
|
In earlier version of fcgid (2.2b) under windows I had to define
| Code: |
FcgidMinProcessesPerClass 0
|
(was DefaultMinClassProcessCount 0) to make sure that the processes dies. Not sure that is still necessary.
Also FcgidBusyTimeout 120 is a bit high. The process waits 2 minutes after the last request until it dies wating for new requests.
The advantage of a longer life time is that apache don't need to start a new process that's why using fcgid instead of cgi  |
|
| Back to top |
|
nikozan
Joined: 23 Apr 2011
Posts: 1
|
|
| Back to top |
|
|
|
|
|
|
