On 7/15/07, <b class="gmail_sendername">Steven Adeff</b> <<a href="mailto:adeffs.mythtv@gmail.com">adeffs.mythtv@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
monit doesn't seem to be monitoring mythbackend. the pid I gave it is<br>correct and gets created by my mythbackend init.d script. but if I<br>kill mythbackend monit never restarts it and the monit web service<br>manager shows that monit doesn't seem to realize its dead. As well, if
<br>I run monit after killing mythbackend the web service manager doesn't<br>show it as being dead but as "running". the web service manager also<br>shows "System" status as always "initializing".
<br><br>anyone have an idea of whats going wrong?<br><br>is there a way to increase the verbosity of the log?<br><br>here's whats in my monitrc,<br><br>################### MythBackend ####################################
<br>check process mythbackend with pidfile /var/run/mythtv/mythbackend.pid<br> group mythtv<br> start program = "/etc/init.d/mythbackend start"<br> stop program = "/etc/init.d/mythbackend stop"<br> if failed port 6544 proto http then restart
<br> if 5 restarts within 5 cycles then timeout<br> depends on mysql<br><br>################### MySQL ####################################<br>check process mysql with pidfile /var/run/mysqld/mysqld.pid<br> group mythtv
<br> start program = "/etc/init.d/mysql start"<br> stop program = "/etc/init.d/mysql stop"<br> if failed port 3306 then restart<br> if 5 restarts within 5 cycles then timeout<br><br><br><br><br>thanks!
<br>--<br>Steve<br></blockquote></div><br>I've got a similar setup and the same results.<br><br>I'm sure this used to work; but lately I find times when the backend process disappears - and I end up restarting by hand.
<br><br>Tom<br>