Thanks for the help! Everything has been stable for a couple nights now. I think a combination of getting the native ruby-mysql drivers compiled and setting the verification_timeout for ActiveRecord did the trick.<br><br>
<div><span class="gmail_quote">On 5/1/06, <b class="gmail_sendername">why the lucky stiff</b> <<a href="mailto:why@ruby-lang.org">why@ruby-lang.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jason Hoffman wrote:<br><br>>>It seems like the mysql tcp connection is dying during the night.<br>>>I'd be<br>>><br>>><br>><br>>interactive_timeout in mysql defaults to 28800 seconds (480 minutes
<br>>or 8 hours).<br>><br>><br>Just raising the interactive_timeout doesn't really solve the problem<br>(while it may appear to.) I would suggest setting the<br>verification_timeout for ActiveRecord. Set it lower than the
<br>interactive_timeout in MySQL.<br><br> ActiveRecord::Base.verification_timeout = 14400<br><br>This will force Rails to reconnect to the database before MySQL can get<br>a chance to timeout.<br><br>_why<br>_______________________________________________
<br>Mongrel-users mailing list<br><a href="mailto:Mongrel-users@rubyforge.org">Mongrel-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/mongrel-users">http://rubyforge.org/mailman/listinfo/mongrel-users
</a><br></blockquote></div><br>