search for: totalmem

...le for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program = "/usr/local/etc/rc.d/lighttpd.sh start" stop program = "/usr/local/etc/rc.d/lighttpd.sh stop" if totalmem > 200.0 MB for 5 cycles then restart group server #check pound process check process pound with pidfile /var/run/pound.pid start program = "/usr/local/etc/rc.d/pound.sh start" stop program = "/usr/local/etc/rc.d/pound.sh stop" if totalmem > 400.0 MB for 5...

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

...tart -d -e production -p 8000 -a 127.0.0.1 -c /home/admin/webapps/gohuman/current -P log/mongrel.8000.pid''" stop program = "/usr/bin/su admin -c ''/usr/local/bin/mongrel_rails stop -c /home/admin/webapps/gohuman/current -P log/mongrel.8000.pid''" if totalmem is greater than 80.0 MB for 5 cycles then alert # 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,...

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

...l_cluster.yml --clean --only 8310" stop program = "/usr/local/bin/mongrel_rails cluster::stop -C /home/valleyc/apps/cms/dev/current/config/mongrel_cluster.yml --clean --only 8310" if failed host 127.0.0.1 port 8310 protocol http with timeout 10 seconds then restart if totalmem > 128 Mb then restart if cpu is greater than 60% for 2 cycles then alert #if cpu > 90% for 5 cycles then restart #if loadavg(5min) greater than 10 for 8 cycles then restart if 3 restarts within 5 cycles then timeout ---------------------------------------------------------------------...

...-a 127.0.0.1 -l log/mongrel.log -P /var/run/mongrel/mongrel.9009.pid -c /home/app/current" stop program = "/usr/local/bin/mongrel_rails stop -P /var/run/mongrel/mongrel.9009.pid" if failed host 127.0.0.1 port 9001 protocol http with timeout 10 seconds then restart if totalmem > 128 Mb then restart if cpu is greater than 60% for 2 cycles then alert if cpu > 90% for 5 cycles then restart if loadavg(5min) greater than 10 for 8 cycles then restart if 3 restarts within 5 cycles then timeout Part of my confusion is if I should use mongrel_rails cluster::start...

...ter/mongrel.9000.pid start program = "/usr/local/bin/mongrel_rails cluster::start -C /etc/mongrel_cluster/mongrel_cluster.yml --clean --only 9000" stop program = "/usr/local/bin/mongrel_rails cluster::stop -C /etc/mongrel_cluster/mongrel_cluster.yml --clean --only 9000" if totalmem is greater than 110.0 MB for 3 cycles then restart # eating up memory? 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 grou...

...idfile /path_to_merb_app/log/merb. 4000.pid start program = " /usr/bin/merb -u nobody -G nogroup -e production -d -m /path_to_merb_app/ -f /path_to_merb_app/dist/conf/upload.conf -M /path_to_merb_app/dist/ conf/merb.yml" stop program = "/usr/bin/merb -k 4000" if totalmem is greater than 95.0 MB for 2 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 t...

...process backgroundrb_11006 with pidfile "/home/user/site/tmp/pids/backgroundrb_11006.pid" start = "/usr/bin/ruby /home/user/site/script/backgroundrb start" stop = "/usr/bin/ruby /home/user/site/script/backgroundrb stop" if cpu > 90% for 2 cycles then restart if totalmem > 512 MB for 2 cycles then restart if 4 restarts within 4 cycles then timeout group backgroundrb I have a non custom location for my some of my gems like packet (/home/ user/.gem/ruby/1.8/bin), and I suspect that part of the problem is that monit uses a spartan PATH (To quote http://mmonit....

Hi, It seems that allocating dedicated memory and cpu(s) is recommended for IO intensive guests (why would I not assume it won''t be?) How can I calculate the amount of memory and cpu to allocate for Dom-0? Is there a formula we can use for this? If there is no known defined formula, isn''t it better to allocate using xm m-set and vcpu-set, versus on boot-time? So you can at

I am comparing two different algorithms in terms of speed and memory usage. I can calculate the processing time with proc.time() as follows but am not sure how to calculate the memory usage. ptm <- proc.time() x <- rnorm(1000000) proc.time() - ptm I would like to be within R itself since I will test the algorithm several hundred times and in batch mode. So manually looking up

I have Mongrel Cluster setup with Apache a mod_proxy_balancer. I''ve seen (from time to time) mongrel instances become non-responsive. Is there anyway to configure the balancer so that it "knows" which processes are no longer good and stops trying to use them? _______________________________________________________ The FREE service that prevents junk email

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first