[Mongrel] best practices for monitoring mongrels with monit?
Nathan Esquenazi
lists at ruby-forum.com
Sun Mar 9 00:31:44 EST 2008
Here is a good recipe for a mongrel process, as provided on some site I
found:
(I believe the forum post was by Ezra)
check process mongrel_cluster_8000
with pidfile /var/apps/twocb/shared/pids/mongrel.8000.pid
start program = "/usr/bin/mongrel_rails cluster::start -C
/var/apps/twocb/current/config/mongrel_cluster.yml --clean --only 8000"
stop program = "/usr/bin/mongrel_rails cluster::stop -C
/var/apps/twocb/current/config/mongrel_cluster.yml --clean --only 8000"
if totalmem is greater than 110.0 MB for 4 cycles then restart
# eating up memory?
if cpu is greater than 50% for 2 cycles then alert
# send an email to admin
if cpu is greater than 80% for 3 cycles then restart
# hung process?
if loadavg(5min) greater than 10 for 8 cycles then restart
# bad, bad, bad
if 20 restarts within 20 cycles then timeout
# something is wrong, call the sys-admin
group mongrel_cluster
--
Posted via http://www.ruby-forum.com/.
More information about the Mongrel-users
mailing list