I tried Min on my test server and it didn't work for me, so I can at least confirm you aren't crazy :)
================================================= Steven Barre, RHCE steven@xxxxxxxxxxxxxxxxxxxxxxxx Systems Administrator Real Estate Webmasters - 250-753-9893 ================================================== On 2015-12-28 11:28, Kevin Burnett wrote:
i'm using apache 2.4.7, mod_fcgid 2.3.9, and ubuntu 14.04.3. FcgidMinProcessesPerClass is supposed to provide a floor, such that no *fewer* than that number of workers will run. did you mean fewer when you said "can confirm I don't get more than FcgidMinProcessesPerClass PHP workers on that site"? i'm not using SuExec, so my setup is more vanilla mod_fcgid running the application as the www-data user. On Mon, Dec 28, 2015 at 2:18 PM, Steven Barre <steven@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:What versions are you using? I've got Server Version: Apache/2.2.15 (Unix) mod_fcgid/2.3.9 running on CentOS 6 I'm also using SuExec to run each domain as a separate user with a separate wrapper. https://bz.apache.org/bugzilla/show_bug.cgi?id=49902 mentions that In mod_fcgid-2.2 processess started by fcgiwrapper were of the same class if they were run with same wrapper by the same owner. In mod_fcgid-2.3 these processess have different class also if they are run in different virtual hosts. But it looks like they fixed the bug in 2.3.7. I just ran a test with a php script doing sleep(10); and can confirm I don't get more than FcgidMinProcessesPerClass PHP workers on that site. ================================================= Steven Barre, RHCE steven@xxxxxxxxxxxxxxxxxxxxxxxx Systems Administrator Real Estate Webmasters - 250-753-9893 ================================================== On 2015-12-28 10:39, Kevin Burnett wrote: Thanks for the response, Steven. Alas, it is supposed to work anywhere in server config, per the docs, and I added it to the VirtualHost section of the app in question (https://github.com/burnettk/repro-mod-fcgid-bug/commit/f03d29d6ab939f67c22b6d03f6eeced259a5aec3), and it still doesn't seem to keep five processes running. On Mon, Dec 28, 2015 at 12:30 PM, Steven Barre <steven@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: I've found it works when defined inside a VirtualHost section, but not when defined globally in a server conf file. ================================================= Steven Barre, RHCE steven@xxxxxxxxxxxxxxxxxxxxxxxx Systems Administrator Real Estate Webmasters - 250-753-9893 ================================================== On 2015-12-28 09:21, Kevin Burnett wrote: Greetings, If I set FcgidMinProcessesPerClass to 5, it doesn't maintain 5 application worker processes at apache startup time or otherwise. It starts with 0 workers, when I hit the app with one curl, it starts up one, and when I hit the app with 10 concurrent connections, it fires up nine workers, which are reaped after FcgidIdleTimeout, bringing the count back down to 1 (docs for FcgidIdleTimeout claim it should respect FcgidMinProcessesPerClass). Keeping the count below a defined limit via FcgidMaxProcessesPerClass seems to work fine. But its sister property, FcgidMinProcessesPerClass, documented at http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidminprocessesperclass, doesn't behave as I would expect. I'm running a rails 4.2 app on apache 2.4.7, mod_fcgid 2.3.9, and ubuntu 14.04.3. I created this docker project to demonstrate what I'm seeing: https://github.com/burnettk/repro-mod-fcgid-bug/blob/master/README.md. You can dig around in the github project or actually fire up the docker container following the steps in the README and inspect all of the configs I haven't explicitly defined. So I'm wondering if FcgidMinProcessesPerClass works for anyone else (I decided to start here before filing a bug), and, if it can work, if you can spot the misconfiguration preventing it from working in the above steps. Thanks! KB --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|