[monit] Re: Problem with monit's "not monitoring" status

[David Bristow]

Anybody have any ideas about this?  It's an intermittent problem for us.

On Tue, Mar 23, 2010 at 12:47 PM, David Bristow <address@hidden> wrote:
> We are running monit v5.1.1 now.  I have another incident where monit
> status was showing a service down, but it should have been started.
> Here are the details:
>
> /var/log/monit.log at around the right time:
>
> [EDT Mar 22 10:47:12] debug    : stop service 'backgroundrb' on user request
> [EDT Mar 22 10:47:12] info     : monit daemon at 11112 awakened
> [EDT Mar 22 10:47:32] error    : 'memcached_fragments' failed to start
> [EDT Mar 22 10:47:32] info     : 'backgroundrb' stop:
> /usr/local/bin/backgroundrb_wrapper
> [EDT Mar 22 10:47:42] debug    : start service 'backgroundrb' on user request
> [EDT Mar 22 10:47:42] info     : monit daemon at 11112 awakened
> [EDT Mar 22 10:47:47] info     : 'backgroundrb' start action done
> [EDT Mar 22 10:47:47] info     : Awakened by User defined signal 1
>
> This is the log entry from when I had to manually run "monit start
> backgroundrb":
>
> [EDT Mar 22 10:59:08] debug    : start service 'backgroundrb' on user request
> [EDT Mar 22 10:59:08] info     : monit daemon at 11112 awakened
> [EDT Mar 22 10:59:08] info     : Awakened by User defined signal 1
> [EDT Mar 22 10:59:08] info     : 'backgroundrb' start:
> /usr/local/bin/backgroundrb_wrapper
> [EDT Mar 22 10:59:20] info     : 'backgroundrb' start action done
>
> backgroundrb file is from /etc/monit.d/
>
> monit status output from when I got alerted about the service being down
>
> The server's /etc/monitrc
>
> Let us know if you need more.
>
> --
> David Bristow <address@hidden>
>



-- 
David Bristow <address@hidden>