Hi all,
We use mongrel behind apache (using mod_proxy_balancer) to run an
internal
app for our business. Lately we’ve been seeing frequent errors from some
of
our mongrel processes.
[Sun Dec 16 08:48:47 2007] [error] [client ] (70007)The timeout
specified has expired: proxy: error reading status line from remote
server
127.0.0.1, referer: http://
[Sun Dec 16 08:48:47 2007] [error] [client ] proxy: Error
reading
from remote server returned by /, referer:
http://
[Sun Dec 16 08:49:08 2007] [error] [client ] (70007)The timeout
specified has expired: proxy: error reading status line from remote
server
127.0.0.1
[Sun Dec 16 08:49:08 2007] [error] [client ] proxy: Error
reading
from remote server returned by /
The problem seems to be that the long-running request hogs a mongrel
process, and when apache sends the next request to it (after a
round-robin
tour through the other 9 mongrels), that request times out too. The
original
action eventually comes back, but sometimes not for several minutes, so
we
can timeout on many requests in a row.
I’ve seen problems like this mentioned in the context of file uploads
(which
explain some of our long-running requests), but I’ve never seen a fix
posted. Maybe I haven’t looked hard enough? Does anyone know of a config
fix
that will skip over these blocked processes?
Thanks!
Mike