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.

On 5/1/06, why the lucky stiff <[EMAIL PROTECTED]> wrote:
Jason Hoffman wrote:

>>It seems like the mysql tcp connection is dying during the night.
>>I'd be
>>
>>
>
>interactive_timeout in mysql defaults to 28800 seconds (480 minutes
>or 8 hours).
>
>
Just raising the interactive_timeout doesn't really solve the problem
(while it may appear to.)  I would suggest setting the
verification_timeout for ActiveRecord.  Set it lower than the
interactive_timeout in MySQL.

  ActiveRecord::Base.verification_timeout = 14400

This will force Rails to reconnect to the database before MySQL can get
a chance to timeout.

_why
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to