Comments on: Monit makes Mongrel play nice!

By: Aninda

Aninda — Fri, 18 Sep 2009 06:01:04 +0000

ahh … i see … i have to exec a script for the failure condition.

It would be nice though if I could specify a file location to be sent as an email attachment in the mail-format.

Thanks for your quick reply!

By: Ilya Grigorik

Ilya Grigorik — Fri, 18 Sep 2009 05:56:19 +0000

Aninda, yes you could do that by creating a script to do the necessary work (extract data from log file, prepare email, send email) and then invoking that script as a condition for the event under monit / god / whichever monitoring system you’re using.

By: Aninda

Aninda — Fri, 18 Sep 2009 05:29:41 +0000

Very nice!
Would it also be possible to send a mongrel log file as an attachment to the alert email?

How could I do something like that?

Thanks.

By: Chris Trinh

Chris Trinh — Thu, 02 Apr 2009 06:25:37 +0000

Thank you for the great article/tut! I’ve learned quite a few new things from it. I just want to add you should probably do this instead after setting up a mongrel_cluster.

start program = “/usr/bin/mongrel_rails cluster::start -C /home/yourapp/config/mongrel_cluster.yml –clean –only 9000″
stop program = “/usr/bin/mongrel_rails cluster::stop -C /home/yourapp/config/mongrel_cluster.yml –clean –only 9000″

For every port/process in your mongrel cluster. Other than that everything else works like a charm. You do need to have the lastest version of mongrel_cluster to use the option –clean. This helps clean out those pesky rouge pid files store in your tmp. For whatever reason that they still persist in the tmp/pid. Its not wise but I tested monit out by “kill -9″ processes in the cluster one at a time, and watch it bring it back to life, all the while giving me alerts =).

I’m fairly new to RoR so my understanding of all this maybe be hazardous to your production sever.

By: Monit and Mongrel - betweenGo

Monit and Mongrel - betweenGo — Mon, 12 Jan 2009 21:06:54 +0000

[...] by Frank Kim on May.27, 2008, under Ruby on Rails This post about Monit and Mongrel is based on this fantastic post, Monit makes Mongrel play nice! [...]

By: Mongrel freezing - monitoring tools « Vlad Zloteanu’s Technical Blog

Mongrel freezing - monitoring tools « Vlad Zloteanu’s Technical Blog — Fri, 26 Dec 2008 12:58:42 +0000

[...] http://www.igvita.com/2006/11/07/monit-makes-mongrel-play-nice/ - The Monit project, described with a small tutorial [...]

By: Ilya Grigorik

Ilya Grigorik — Fri, 19 Dec 2008 13:45:44 +0000

Marcelo, you might want to try the monit newsgroup, it sounds like a debugging question. Have you tried running monit in ‘verbose’ mode to see more details?

By: Marcelo Marqueti

Marcelo Marqueti — Sun, 14 Dec 2008 16:22:31 +0000

Hi,
I tring to use monit, I can start and stop the mongrel with monit with this command line:

check process mongrel_3001 with pidfile /home/mongrel/testmongrel/tmp/pids/mongrel.3001.pid

start program = “/usr/bin/mongrel_rails cluster::start -C /etc/mongrel_cluster/testmongrel.yml –clean”
stop program = “/usr/bin/mongrel_rails cluster::stop -C /etc/mongrel_cluster/testmongrel.yml –clean”

But the error message I get this error yet ‘mongrel_3001′ failed to start.
The servers starts, but the monit daemon dont start.
I try monit status and I get a error, the daemon not running.

By: Nash Kabbara

Nash Kabbara — Sat, 06 Sep 2008 19:02:11 +0000

Referring to the patch.
unless `ps axo pid= | grep #{pid} | grep -v grep`.length > 0 is safer.

ps ax alone will include the name of all processes which could have arguments that include the pid number.

By: D. Rothlisberger

D. Rothlisberger — Mon, 07 Jul 2008 14:48:28 +0000

If you are trying to configure monit to start your mongrels and it simply won’t (with no complaints from monit) check your mongrel logs.

I had to set my monit config’s start line to something like this:
start = "/usr/bin/env PATH=$PATH:/usr/local/bin HOME=/home/user /usr/local/bin/mongrel_rails cluster::start -C /home/user/path/to/app/config/mongrel_cluster.yml --only 8000"