[mythtv-users] monit on ubuntu not working...

[Andrew Williams]

On 7/17/07, Tom Greer <trgreer at gmail.com> wrote:

> On 7/17/07, Andrew Williams <lists at nikdoof.net> wrote:
> >
> >  disappointing, but at least I'm not alone. I'll assume ubuntu's
> > > package of monit is messed up.
> >
> >
> > The default cycle time for Monit is 120 seconds, so it'll take a while
> > before monit notices, i've reduced my cycle down to 20 seconds. Check your
> > syslog to see if its actually picking up that the process has died.
> >
> >
>
> The cycle time is not the problem.  This used to work.  Monit no longer
> seems to notice that the mythbackend has died.
>
> I have not had any time to troubleshoot.   I just keep restarting backends
> when I find one that is not running.
>
> Has anyone checked to see whether myth has modified its response to the
> port that monit is testing?
>
> Any help is appreciated.


You need to check a few things:


   1. Do you get any syslog output saying its died?
   2. Is the PID file valid?
   3. Are all your locations correct in the monit config

Bar that, theres not much else you can investigate, i suspect its down to
either the PID or init script path being wrong. Heres my config:


> check process mythbackend with pidfile /var/run/mythtv/mythbackend.pid
>  group mythtv
>  start program = "/etc/init.d/mythtv-backend restart"
>  stop program  = "/etc/init.d/mythtv-backend stop"
>  if failed port 6544 proto http then restart
>  if memory is greater than 50% for 10 cycles then exec
> "/usr/local/bin/monit-mythcheck"
>  depends on mysql
>
> check process mysql with pidfile /var/run/mysqld/mysqld.pid
>  group mythtv
>  start program = "/etc/init.d/mysql start"
>  stop program = "/etc/init.d/mysql stop"
>  if failed port 3306 then restart
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070717/d3a0849a/attachment.htm