Thanks guys - this works great for me. Much appreciated.
Mike On Thu, Mar 27, 2008 at 3:06 PM, Steve Midgley <[EMAIL PROTECTED]> wrote: > At 11:50 AM 3/27/2008, [EMAIL PROTECTED] wrote: > >Date: Thu, 27 Mar 2008 11:49:00 -0700 > >From: Andy Koch <[EMAIL PROTECTED]> > >Subject: Re: [Mongrel] best practices for monitoring mongrels with > > monit? > >To: mongrel-users@rubyforge.org > >Message-ID: <[EMAIL PROTECTED]> > >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > >here's a blog post on suppressing the logging... > > > >"http://www.ruby-forum.com/topic/95146"; > > > >here's my bit from my monitrc > > > >****************** > >if failed port 8000 protocol http and request "/pulse" > > with timeout 10 seconds > > then restart > >******************* > > > > where "pulse" is defined in my routes.rb > > Hi, > > I wrote a very simple Rails controller (+ test!) that lets my load > balancers check that my stack is up. Note that I intentionally make a > database call here b/c I want this monitor to fail if the db is not up. > But you could easily remove that part of the system. I chose > "schema_info" to query b/c it's always available in Rails and as small > as can be. > > http://pastie.caboo.se/132646 > > hth, > > Steve > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
