similar to: Monit; BackgroundRB; environment variables

I did some googling and found a post where Ezra said he monitors backgroundrb for memory/cpu/uptime. Just wondering what some reasonable starting points would be. Pat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Anyone have a a good monit config section for bgrb? 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

Hi everyone, I''m trying to use monit to monitor a backgroundrb process (that gets killed occasionally), but I cant seem to seem the start or stop commands to work (i simply get ''execution failed'') - though they do work fine from the command prompt. I''m not doing anything particularly sophisticated: check process backgroundrb_11006 with pidfile

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Might there be anything CentOS related on why I cannot access the Monit GUI system on http://box-running-monit.com:2812 ? I am using a very basic /etc/monit.conf config, but I cannot get it serve the web page on my box The service start and stops fine (e.g. "/etc/init.d/monit start"), and I have it set to listen to port 2812 in the "/etc/monit.conf file" (so far, kept the

Has anybody here tried the "Monit" utility (http://mmonit.com/monit/)? I need to set up some kind of "watchdog" functionality for a custom service otherwise started via init (i.e. via a script in /etc/init.d + rc*.d links managed by chkconfig) and it seems like this system may give me nearly what I want. However, something that concerns me about it, is that it appears to

Monit 4.9, Mongrel 1.0.1, Rails 1.2.6, Mac OS X 10.4.11 (PPC) I don''t know whether this is a mongrel issue or a monit issue. I''m trying to poke my way around a system set up by someone else. I have no more experience w/ mongrel that local Rails dev at this point, and a conceptual understanding of how monit is working. I have the Deploying Rails beta book, and I''m

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Howdy, I''m trying to use monit with backgroundrb, but it seems that backgroundrb.ppid isn''t holding the id of the backgroundrb task. jodi at soup/var/www/the-soup/current $ cat log/backgroundrb.ppid 23182 jodi at soup/var/www/the-soup/current $ ps -efl 1 S deploy 23184 1 0 75 0 - 27056 stext 11:27 ? 00:00:04 backgroundrb 1 S deploy 23186 23184 0 76

Hi there, I would like to config Monit to monitor our production-unicorn-workers What memory size would you recommend to be the maximum reachable for a worker? so Monit can restart it. Thanks a lot ! Manuel Palenciano

On one of my development servers mongrel dies when idle for any length of time. Since I''ve not been able to solve that problem I thought I''d route around it by using monit to kick things when necessary. My monitrc contains the following... -------------------------------------------------------------------------------- check process mongrel_8310 with pidfile

Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

Hi list , I'm trying to run monit with asterisk, starting as simple # My PBX Asterisk check process asterisk with pidfile /var/run/asterisk/asterisk.pid start program = "/etc/init.d/asterisk start" with timeout 60 seconds stop program = "/etc/init.d/asterisk stop" with timeout 60 seconds if failed host 127.0.0.1 port 5038 then restart if 5 restarts within 5 cycles then

Hi! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =

I need lsb compliant start/stop scripts so I can successfully use things like monit and heartbeat, so I updated backgroundrb''s newer start/stop module to be more lsb compliant. Specifically, my version 1) responds to status and restart 2) start cleans the old pidfile in case of dead/crased process, and 3) made stop exit 0 if already stopped. Also, unrelated to lsb compliance but

Greetings all, Unit tests are passing, but I''m having mucho problems getting brb to run without exceptions for more than 6 hours. I''m seeing a mixture of the following 2 exceptions: 20070605-11:26:56 (21497) failed to find slave socket - (RuntimeError) 20070605-11:26:56 (21497) /usr/local/lib/ruby/gems/1.8/gems/ slave-1.2.1/lib/slave.rb:435:in `initialize''

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

Hey All, I just wanted to get other peoples take on problems when running merb in production? Just as Rails used to do, the mongrels tend to get heavy/unresponsive over time so need a good kicking by a watcher daemon like god or monit. However, I have had serious problems getting God to restart the process, as the "merb -k <port>" command doesnt appear to work reliably