On Jun 5, 2005, at 1:12 PM, David Thomson wrote:
> Hi all,
>
> I''ve got a fairly standard SuSE Linux + Apache + FastCGI setup on
my
> server, on which I have one Rails app already running on FastCGI.
> I''ve deployed another app to the server, but it won''t run
under
> FastCGI; it works fine under standard CGI, but I get the following
> errors:
>
> FastCGI: comm with (dynamic) server "/srv/www/thinkstitute/ta
> da/public/dispatch.fcgi" aborted: (first read) idle timeout (30 sec)
> FastCGI: incomplete headers (0 bytes) received from server "/
> srv/www/thinkstitute/tada/public/dispatch.fcgi"
>
> I can''t see any differences in terms of setup or permissions or
> anything like that between the two apps.
>
> I''ve seen some other mentions of this on the mailing list, but not
> anything definitive answer-wise, so apologies for repeating the
> question (and/or if I''ve missed an answer).
Hi David,
Just increase the idle time from the default 30 seconds. For example,
one of my configs:
<IfModule mod_fastcgi.c>
FastCgiIpcDir /usr/local/www/fcgi_ipc/tmp
AddHandler fastcgi-script .fcgi
FastCgiSuexec /usr/local/sbin/suexec
FastCgiConfig -singleThreshold 100 -killInterval 300 -autoUpdate -
idle-timeout 240 -pass-header HTTP_AUTHORIZATION
</IfModule>
And remember that FastCgiConfig is only for dynamically spawned
fastcgis.
It''s shown up before: http://weblog.rubyonrails.com/archives/
2005/01/03/watch-for-huge-requests-on-default-fcgi/
Cheers, Jason