On 7/17/07, <b class="gmail_sendername">Andrew Williams</b> <<a href="mailto:lists@nikdoof.net">lists@nikdoof.net</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;">
<div><span class="q">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">disappointing, but at least I'm not alone. I'll assume ubuntu's<br>package of monit is messed up.
</blockquote>
<div> </div></span>
<div>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.
</div>
<div> </div></div></blockquote></div><br>The cycle time is not the problem. This used to work. Monit no longer seems to notice that the mythbackend has died.<br><br>I have not had any time to troubleshoot. I just keep restarting backends when I find one that is not running.
<br><br>Has anyone checked to see whether myth has modified its response to the port that monit is testing?<br><br>Any help is appreciated. <br><br>Tom<br><br><br>