Anyone have a a good monit config section for backgroundrb?
I'm thinking something like this:
check process backgroundrb with pidfile
/var/www/apps/foo/current/log/backgroundrb.pid
start program = "/var/www/apps/foo/current/script/backgroundrb start"
stop program = "/var/www/apps/foo/current/script/backgroundrb stop"
if failed host 127.0.0.1 port 2000 then restart
if 5 restarts within 5 cycles then timeout
Problem is the port test fails - I thought 2000 is the default...
Thanks,
Zack-
It depends on what version fo the plugin you are using. The 0.2.x branch uses 2000 by default *but* it also uses unix domain sockets by default. So it really is not listening on any port, its using socket files to do its communicating. I havent gotten monit port checking to work with bdrb so I just monito it for memory and cpu and uptime.
Cheers-
-- Ezra Zygmuntowicz-- Lead Rails Evangelist
-- ez@engineyard.com
-- Engine Yard, Serious Rails Hosting
-- (866) 518-YARD (9273)
> Anyone have a a good monit config section for backgroundrb?
>
> I'm thinking something like this:
>
> check process backgroundrb with pidfile
> /var/www/apps/foo/current/log/backgroundrb.pid
> start program = "/var/www/apps/foo/current/script/backgroundrb
> start"
> stop program = "/var/www/apps/foo/current/script/backgroundrb stop"
> if failed host 127.0.0.1 port 2000 then restart
> if 5 restarts within 5 cycles then timeout
>
> Problem is the port test fails - I thought 2000 is the default...
>
> Thanks,
>
> --
> Zack Chandler
> http://depixelate.com
Zack-
It depends on what version fo the plugin you are using. The 0.2.x
branch uses 2000 by default *but* it also uses unix domain sockets by
default. So it really is not listening on any port, its using socket
files to do its communicating. I havent gotten monit port checking to
work with bdrb so I just monito it for memory and cpu and uptime.
Cheers-
-- Ezra Zygmuntowicz
Ezra,
Thanks - I had read about 0.2.x using domain sockets but had
promptly forgot when updating my monit config.
Thanks,