similar to: monit paths

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 =

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

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

greetings, i have been trying to get merb and monit to play well. but monit won''t restart merb. neither will monit stop merb if it is still running but not responding. below is the monit config for the merb app. anyone know what i am doing wrong or have good strategies for using monit and merb? thank you - john weir check process manwith-4000 with pidfile

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

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 =>

I started emailing monit mailing list because I started getting this problem where I couldn''t start backgroundrb with monit anymore, thinking it was a monit problem. However, I back tracked a bit since I had added code to my project, and monit was able to start backgroundrb again. I seem to have zeroed in on the problem. I''m not sure where the problem lies - maybe monit or

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

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

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

On 01/11/2015 01:04 PM, Sven Kieske wrote: > 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

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

_**_So I have epel enabled on this centos 6 server, but yum -y install monit will not install monit. yum search monit does not show monit as available to be installed. [root at lb1 ~]# yum install monit Loaded plugins: fastestmirror, presto Setting up Install Process Loading mirror speeds from cached hostfile * base: mirror-centos.hostingswift.com * epel: reflector.westga.edu * extras:

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

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

Hello, When I upgraded my servers to dovecot 2.2.13 the monitoring tool monit started to send out warnings that it couldn't reach my imap/pop3 servers through ssl any more. The same problem didn't happen on non-ssl-connections. According to people on the monit list this is likely a dovecot issue: https://lists.gnu.org/archive/html/monit-general/2014-06/msg00031.html Let me quote: >

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

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

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