On Mon, 2006-06-12 at 13:51 +0100, Ross Riley wrote:> Hello.
>
> Been getting the dreaded MySQL broken pipe error after a few hours of
> the app being started. Obviously restarting the server fixes
> everything. I gather from a few posts about running rails on fast-cgi
> that this happens when mysql timesout before the application. Just
> wondering what the timeout for mongrel is and which mysql variable it
> has to be lower than.
There is no "timeout" in mongrel other than in the rare condition
where
mongrel is overloaded with too many connections and any current
connections have taken too long. These are set with the -n and -t
options.
You are most likely running into:
http://mongrel.rubyforge.org/faq.html
"Q: Mongrel stops working if it?s left alone for a long time."
Read that, and there were quite a few posts to the mailing list on the
subject last month or so (google loves you because I''m lazy).
--
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/