On Wed, Mar 10, 2010 at 9:04 AM, Steve Rippl <rip...@woodlandschools.org> wrote: > Hi, > > I wonder if anyone with FastCGI experience recognizes what these are about? > > (error log for my apps VirtualHost) > > [Wed Mar 10 08:14:35 2010] [error] [client 10.22.0.85] FastCGI: comm with > server "/srv/WsdSis/script/wsdsis_fastcgi.pl" aborted: idle timeout (30 > sec), referer: http://[--snip--]/sections/report/48/119813 > [Wed Mar 10 08:14:35 2010] [error] [client 10.22.0.85] FastCGI: incomplete > headers (0 bytes) received from server > "/srv/WsdSis/script/wsdsis_fastcgi.pl", referer: > http://[--snip--]/sections/report/48/119813 > [Wed Mar 10 08:14:36 2010] [error] [client 10.22.0.85] FastCGI: comm with > server "/srv/WsdSis/script/wsdsis_fastcgi.pl" aborted: idle timeout (30 > sec), referer: http://[--snip--]/sections/report/48/119813 > [Wed Mar 10 08:14:36 2010] [error] [client 10.22.0.85] FastCGI: incomplete > headers (0 bytes) received from server > "/srv/WsdSis/script/wsdsis_fastcgi.pl", referer: > http://[--snip--]/sections/report/48/119813 > > Something is taking too long?!! > > I'm using libapache2-mod-fastcgi 2.4.6.99~snap20081109 (kindly provided by > Andrew Roland) on Debian 5 > > Thanks, > Steve Rippl > > > -- > Steve Rippl > Technology Director > Woodland Public Schools > 360 225 9451 x326 > >
Hi Steve, That just means that your FastCGI job hasn't sent a response within 30 seconds, and so it assumes the process is stuck. You can adjust this with the -idle-timeout option, see: http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiServer Although it may be better to get your report running faster. If you use DBIC, you can use QueryLog (which integrates very nicely into Catalyst) to track down slow queries. -J _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
