<br><br><div><span class="gmail_quote">On 7/26/07, <b class="gmail_sendername">Peter Schachte</b> <<a href="mailto:schachte@csse.unimelb.edu.au">schachte@csse.unimelb.edu.au</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Phil Figgins wrote:<br><br>> My current "fix" when the wife & kids say "the tv's broke again" is to fire<br>> up TeraTerm and run "/etc/init.d/mythbackend restart". The stop of the
<br>> mythbackend service fails each time since it's already dead.<br><br>I can't help you with the random backend crashes (I've got a similar problem,<br>and haven't been able to track it down either). But I suggest installing monit
<br>to restart the backend when it crashes. See<br><br> <a href="http://www.mythtv.org/wiki/index.php/StatusMonitoringHowTo">http://www.mythtv.org/wiki/index.php/StatusMonitoringHowTo</a><br><br><br></blockquote></div>
This wiki was a little frustrating but I finally got something working with monit.<br><br>1) as far as I can tell, the command "monit monitor mythbackend" does nothing unless you have already manually typed monit to start the daemon.
<br><br>2) I believe there is an error in the supplied monitrc file in that the mysql command does not have "start" or "stop" arguments.<br><br>Once I commented out the mysql portion of monitrc (and the depend statement), typed monit to start the daemon, then went onto the web page to manually start monitoring mythbackend, monit indicated it was now monitoring mythbackend.
<br><br>I haven't tested the init.d portion yet...<br>________________________<br>"It's easy enough to name those who would piss themselves with joy over the prospect of a One World corporate state, with billions of people begging to work for their 1,500 calories a day and an xBox chip in their necks."