Re: Debugging comm with (dynamic) server aborted

Hello,

On Tue, 31 Oct 2006 23:15:08 +0900, Bill Moseley <[email protected]> wrote:

> This is Apache2 on Dreamhost (shared hosting)
>
> According to their wiki they say the config is:
>
> FastCgiConfig -autoUpdate -initial-env RAILS_ENV=production  
> -idle-timeout 120 -maxClassProcesses 5 -killInterval 300
>
> At times I see errors like this:
>
> [Tue Oct 31 05:26:34 2006] [error]  FastCGI: comm with (dynamic) server  
> "/home/bmoseley/trac" aborted: (first read) idle timeout (120 sec)
> [Tue Oct 31 05:26:34 2006] [error]  FastCGI: incomplete headers (0  
> bytes) received from server "/home/bmoseley/trac"

[ Snip more details ]

> What causes that "comm with (dynamic) server" error?

The FastCgiConfig's -idle-timeout value is 120 seconds.  This means
that the FastCGI Process Manager will kill any FastCGI request that
fails to respond within 120 seconds.  The second error message
typically follows, when a process is killed for taking too long.

I would check the Apache Error logs and see if Trac is outputting any
interesting errors that might give you a hint at why it is taking so
long.  It may be blocked on a database call or some other resource.

Good luck!
Zev
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/