Does anyone have any tips for checking to see if the mongrel instance
is responding to HTTP? I just tried doing this:
if failed host 127.0.0.1 port 8001 protocol http
with timeout 10 seconds
then restart
but when I have that code in my monit script it gives me this error:
mongrel_rails_8001' failed protocol test [HTTP] at INET[127.0.0.1:8018] via TCP
Thanks for any tips.
Mike
On Sun, Mar 9, 2008 at 1:31 AM, Nathan Esquenazi <[EMAIL PROTECTED]> wrote:
> 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/.
> _______________________________________________
> Mongrel-users mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
