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

[David Bristow]

We are having trouble with certain services managed by monit that do
not restart as they should after being shut down and then started up
again.

For example, we use backgroundrb.  Someone shut it down for updating,
and started it up afterwards.  Here is a sample section of the
monit.log  that shows what was happening at the time:

[EST Feb 19 11:44:48] debug    : stop service 'backgroundrb' on user request
[EST Feb 19 11:44:48] info     : monit daemon at 19023 awakened
[EST Feb 19 11:45:10] error    : 'syslog-ng' failed to start
[EST Feb 19 11:45:10] info     : 'backgroundrb' stop:
/usr/local/bin/backgroundrb_wrapper
[EST Feb 19 11:45:19] debug    : start service 'backgroundrb' on user request
[EST Feb 19 11:45:19] info     : monit daemon at 19023 awakened
[EST Feb 19 11:45:31] info     : 'backgroundrb' start action done
[EST Feb 19 11:45:32] info     : Awakened by User defined signal 1

And at 12:09AM, this is the "monit status" for backgroundrb:

Process 'backgroundrb'
  status                            not monitored
  monitoring status                 not monitored
  data collected                    Fri Feb 19 12:08:33 2010

Why does this happen?  We are using monit 5.0.3.

-- 
David Bristow <address@hidden>