Becoming dramatic here, already running over 30 processes. Running out
of memory this way.
All time high here is 5 processes, and while writing this mail it is
already 34 and all 34 have an entry in the mod_status page.
Also looks like it is not stopping/killing processes any more, have
entries with 1784 seconds idle (FcgidIdleTimeout is default, 300)
Going back to 2.3.7 at AL.
On Sunday 29/09/2013 at 21:15, Steffen wrote:
Observe a different behavior compared to 2.3.7
- It spawns a lot more mod_fcgid processes, looks like vhost is in
charge (mod_fcgid only global defined here)
- I see in Windows taskmanager and in mod_status 5 processes and the
error log says that the are 3 started, a mismatch.
- Also different in mod_status page, see more then one entry for
Process: php-cgi.exe
With 2.3.8 splitted now :
Total FastCGI processes: 5
Process: php-cgi.exe (d:/servers/apache/php/php-cgi.exe)
Pid Active Idle Accesses State
4620 487 43 17 Ready
Process: php-cgi.exe (d:/servers/apache/php/php-cgi.exe)
Pid Active Idle Accesses State
3840 515 109 5 Ready
Process: php-cgi.exe (d:/servers/apache/php/php-cgi.exe)
Pid Active Idle Accesses State
6552 557 456 6 Ready
Process: php-cgi.exe (d:/servers/apache/php/php-cgi.exe)
Pid Active Idle Accesses State
3204 1962 7 187 Ready
5036 2143 17 192 Ready
With 2.3.7 was only one entry, like:
Process: php-cgi.exe (d:/servers/apache/php/php-cgi.exe)
Pid Active Idle Accesses State
3204 1962 7 187 Ready
5036 2143 17 192 Ready
...
Not really trust 2.3.8 (yet), give me a few days to observe more.
On Sunday 29/09/2013 at 20:01, Jeff Trawick wrote:
Tarballs/zips are at http://httpd.apache.org/dev/dist/mod_fcgid/
Shortcut to changes:
http://httpd.apache.org/dev/dist/mod_fcgid/CHANGES-FCGID
+/-1
[ ] Release mod_fcgid 2.3.8 as GA
I'll hold the vote open for 72 hours unless something out of the
ordinary occurs.
Thanks in advance for testing!
--
Born in Roswell... married an alien...
http://emptyhammock.com/
