[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
problem getting monit to recognize new PID after logroll of monitored ap
From: |
Sennott, Mark |
Subject: |
problem getting monit to recognize new PID after logroll of monitored app |
Date: |
Tue, 3 Jul 2007 15:33:09 -0500 |
Every night I shut down our mongrel processes, archive the logs, and
then restart them. As part of this, I shut down monit before hand and
then start it back up after. Problem is that Monit says that the
processes have NOT started and tries to restart them (even though I have
verified that they are up and running before Monit starts). At first I
thought it was the state file, so I make sure it is deleted when I shut
down monit. Here is what I see in the logs:
[CDT Jul 3 15:24:13] info : Shutting down monit HTTP server
[CDT Jul 3 15:24:13] info : monit HTTP server stopped
[CDT Jul 3 15:24:13] info : monit daemon with pid [21176] killed
[CDT Jul 3 15:24:13] info : Monit stopped
[CDT Jul 3 15:24:44] info : Starting monit daemon with http
interface at [x03.exv.trb:8888]
[CDT Jul 3 15:24:44] info : Starting monit HTTP server at
[x03.exv.trb:8888]
[CDT Jul 3 15:24:44] info : monit HTTP server started
[CDT Jul 3 15:24:44] info : Monit started
[CDT Jul 3 15:24:44] error : 'metromix-9300' process is not running
[CDT Jul 3 15:24:44] info : 'metromix-9300' trying to restart
[CDT Jul 3 15:24:44] info : 'metromix-9300' start:
/usr/local/sbin/metromix_monit
.
.
.
[CDT Jul 3 15:24:49] error : 'metromix-9331' process is not running
[CDT Jul 3 15:24:49] info : 'metromix-9331' trying to restart
[CDT Jul 3 15:24:49] info : 'metromix-9331' start:
/usr/local/sbin/metromix_monit
[CDT Jul 3 15:25:49] info : Monit has not changed
[CDT Jul 3 15:25:49] info : 'metromix-9300' process is running with
pid 23246
[CDT Jul 3 15:25:49] info : 'metromix-9301' process is running with
pid 23249
[CDT Jul 3 15:25:49] info : 'metromix-9302' process is running with
pid 23252
As you can see above, after 60 seconds, monit re-checks and says that
everything is fine. Is it really trying to restart my app or is this
just a fluke with logging?
- problem getting monit to recognize new PID after logroll of monitored app,
Sennott, Mark <=