similar to: mongrel_cluster : up to 500 MiB memory

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

I have just had a server halt itself and it took me some time to notice. I am planning on implementing some application monitoring using an external service that polls the website from outside. If it can''t reach it then it will SMS me or something. (I would like Prowl on my iPhone and Mac at the same time). I could point the monitoring service at one of the application URLs but I

I have this configuration: class monit { # Installing packages. package { "monit": ensure => latest; } file { "/etc/default/monit": owner => "root", group => "root", mode => "0644", source => "puppet:///monit/etc/default/monit", } file { "/etc/monit/monitrc": owner => "root", group =>

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

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

I was playing around with merb over the weekend and whipped up a simple form that takes your mongrel_cluster.yml file and outputs monit files for you. Not exactly earth shattering info, but if you have a couple of pups it might save you some braindead typing. It''s using the new mongrel_cluster syntax, of --only and clean for each port in your system. Hope it saves someone some time.

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

Hi everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11.01.2015 19:05, Valeri Galtsev wrote: > That sounds like you have collected and counted "votes" pro and > against systemd. How could it sound like I collected "votes"? I don't care about votes when it comes to technical superiority. > As far as "advantages" are concerned: I didn't see any compared

Apologizes in advance if this sounds rather dense, but I want to make sure I''m understanding everything correctly. We''re in the process of migrating from Apache2.0/FastCGI to Apache2.0+mongrel (why not 2.2? that story is too long and too uninteresting to recount here, but I will tell you that it involves RHEL and only using RHN rpms). The init script that comes with mongrel

I wanted to be able to specify in my /etc/rc.conf file whether mongrel_cluster should be enabled and the mongrel_cluster_config file for the init script, so I wrote this simple rc.d style script. Just throw it in /usr/local/etc/rc.d/ and do a chmod +x /usr/local/etc/rc.d/mongrel_cluster.sh To enable the script, add mongrel_cluster_enable="YES" to /etc/rc.conf and optionally add

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

Le 08/07/2012 19:50, R?cker Thomas a ?crit : > It sees far less testing and review than mainline. > The other day we had someone for whom Icecast suddenly started crashing. > Turned out it was a kh build. I'll pipe in. The company I work for has 1000+ audio (and some video) streams, serving tens of thousands of listeners per stream, running on both icecast and icecast-kh and _both_

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

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

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start

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

Hello all After installing Mongrel, Mongrel Cluster and all it''s dependencies via gems under FreeBSD. Next I have configured all config/mongrel_cluster.yml for each Rails app, then: % mkdir /usr/local/etc/mongrel_cluster and likend each railsapp.yml to it''s refering app/config/mongrel_cluster.yml My question is, after preparing all base configs now I need to add some rc.d

We''re running a handful of XCP 1.1 pools and have run in to situations wherein the local filesystem on the Dom0 control domain hits 100% capacity due to error logging in /var/log (daemon.log, messages, xensource.log, etc) thereby taking that host offline. Twice recently we''ve run in to this, on two different pools, first due to the primary SR hitting capacity and secondly when

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