Ticket #2060 (closed malfunction: fixed)
increase fastcgi-timeout for user-domains
|Reported by:||joximu||Owned by:||joximu|
|Priority:||normal||Milestone:||ispCP ω 1.0.3|
|Component:||Config Files||Version:||ispCP ω 1.0.3|
|Severity:||Easy||Keywords:||fastcgi timeout, 500|
Description (last modified by joximu) (diff)
Searching for the reason for this:
[Wed Nov 04 09:20:16 2009] [error] [client 184.108.40.206] FastCGI: comm with (dynamic) server "/var/www/fcgi/dom.ch/php5-fcgi-starter" aborted: (first read) idle timeout (30 sec), referer: http://www.dom.ch/db/db.php [Wed Nov 04 09:20:16 2009] [error] [client 220.127.116.11] FastCGI: incomplete headers (0 bytes) received from server "/var/www/fcgi/dom.ch/php5-fcgi-starter", referer: http://www.dom.ch/db/db.php
I found out that the ispcp setup does not have a long timeout for the user-domains. I tried to use php commands to increase max_exec_time, then I tried to figure out why we have only 30 sec - even if FastCgiServer? is configured with 300 sec.
After that I got the solution: According to http://www.fastcgi.com/mod_fastcgi/docs/...stcgi.html
With "FastCgiServer? ... -idle-timeout 300" we only set the timeout of the process manager.
We need to also set the timeout in FastCgiConfig?:
The FastCgiConfig directive defines the default parameters for all dynamic FastCGI applications. This directive does not affect static or external applications in any way.
so it looks like this...
FastCgiConfig -minProcesses 1 \ -maxProcesses 400 \ -maxClassProcesses 5 \ -multiThreshold 80 \ -killInterval 60 \ -startDelay 5 \ -pass-header Authorization \ -idle-timeout 300
Should be no big deal...
If I get some feedback I can include this.