[LRUG] apache 2.0 + mongrel

[Ed Davey]

I had a similar problem on an about-to-be-deployed setup which had long
periods of inactivity. Once I configured my monitoring system to check the
site's availablility every 5 mins the problem was "fixed".

If you're not already using it you might want to look into Monit for
monitoring and restarting services where necessary. Ilya G has a detailed
explanation of how to configure Monit for Mongrel use at: 

http://www.igvita.com/blog/2006/11/07/monit-makes-mongrel-play-nice/

and there's a guide to installing Monit on Debian which covers the Apache
side at:

http://www.debian-administration.org/articles/269

ED


 

> -----Original Message-----
> From: chat-bounces at lrug.org [mailto:chat-bounces at lrug.org] On 
> Behalf Of Andrew Stewart
> Sent: 26 April 2007 09:22
> To: London Ruby Users Group
> Subject: Re: [LRUG] apache 2.0 + mongrel
> 
> 
> > My first thought would be that the mongrel process is being  
> > killed.  Maybe they don't like long running processes and are  
> > killing it every so-often.  You could check with them about their  
> > support for Rails.
> 
> Alternatively your process's memory footprint might be growing  
> through a threshold set by MediaTemple, triggering them to kill it.
> 
> Are you running a third-party Rails app like, for example, Mephisto?
> 
> Regards,
> Andy Stewart
> 
> 
> _______________________________________________
> chat mailing list
> chat at lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>