[Mongrel] Mongrel dying daily with Ruby 1.8.6

Matt Zukowski mzukowski at urbacon.net
Wed Apr 4 10:54:41 EDT 2007

Are you sure this isn't being caused by something unrelated to mongrel
or ruby 1.8.6? We were having a similar problem a while ago and traced
it down mysql closing its connection after 8 hours of inactivity
(ActiveRecord, somewhat stupidly, does not attempt to reconnect the
closed connection).

Pete DeLaurentis wrote:
> Hi guys,
> I've been running mongrel for a while now with Ruby 1.8.4, and last  
> week upgraded to 1.8.6.
> Since upgrading, each morning when I wake up there's a big problem:
> 1. Accessing the site returns a "500 Internal Server Error"
> 2. All the mongrel_rails processes are still running, but none of  
> them are active (when I run top)
> 3. Lighttpd and pound are still running nicely
> 4. There's plenty of free RAM
> 5. There's plenty of free HD
> 6. When I restart mongrel, it all starts working again
> I haven't seen anything like this before.  Does this sound familiar  
> to anyone?
> Thanks for the help,
> Pete
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users

This e-mail message is privileged, confidential and subject to copyright. Any unauthorized use or disclosure is prohibited. 
Le contenu du pr'esent courriel est privil'egi'e, confidentiel et soumis `a des droits d'auteur. Il est interdit de l'utiliser ou de le divulguer sans autorisation.

More information about the Mongrel-users mailing list