[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Monit is starting my process, but then monit itself disappears
From: |
Martin Pala |
Subject: |
Re: Monit is starting my process, but then monit itself disappears |
Date: |
Thu, 5 Jan 2012 22:43:12 +0100 |
Hi,
do you have the "set daemon <number_of_seconds>" in the monit configuration
file? If it is missing, monit will do just one poll.
For example to check the services every 5 seconds add this to the configuration
file:
set daemon 5
Regards,
Martin
On Jan 5, 2012, at 7:04 PM, Matthew Hillsborough wrote:
> Hi all,
>
> I have a process I'm monitoring with ``monit``. Monit has no problem starting
> the process. However, after I start the process, I do not see Monit itself in
> my process list. If I go ahead and kill the process itself, monit does not
> restart it. I am using Monit to monitor ``Resque``. I start it with the
> following command line:
>
> ``monit -c resque.monit``
>
> The resque worker starts, but that's it, it is no longer monitored after.
> Here's the configuration I am using.
>
> check process resque_worker_QUEUE
> with pidfile /Users/foo/MYAPP/tmp/pids/resque_worker_QUEUE.pid
> start program = "/usr/bin/env HOME=/Users/foo RACK_ENV=development
> /bin/sh -l -c 'cd /Users/foo/MYAPP; nohup rvm address@hidden exec bundle exec
> rake environment resque:work RAILS_ENV=development QUEUE=* VERBOSE=1
> PIDFILE=/Users/foo/MYAPP/tmp/pids/resque_worker_QUEUE.pid & >>
> log/resque_worker_QUEUE.log 2>&1'"
> stop program = "/bin/sh -c '/usr/bin/cd /Users/foo/MYAPP &&
> /bin/kill -9 `/bin/cat tmp/pids/resque_worker_QUEUE.pid` && /bin/rm -f
> tmp/pids/resque_worker_QUEUE.pid; exit 0;'"
> if totalmem is greater than 300 MB for 10 cycles then restart #
> eating up memory?
> group resque_workers
>
> Thanks for any and all help,
>
> Matthew
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general