<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 9:10 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">fixed top-posting<br>
<br>
<br>
On 08/05/2013 04:17 PM, George Galt wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Mon, Aug 5, 2013 at 4:15 PM, Raymond Wagner wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 8/5/2013 4:09 PM, George Galt wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
and I'm getting new logs every 10 minutes:<br>
-rw-rw-r--. 1 mythtv mythtv 12782 Aug 4 00:00<br></div>
mythbackend.20130804035006.**<u></u>890.log<div class="im"><br>
-rw-rw-r--. 1 mythtv mythtv 8616 Aug 4 00:10<br></div>
mythbackend.20130804040009.**<u></u>1065.log<div class="im"><br>
-rw-rw-r--. 1 mythtv mythtv 9707 Aug 4 00:20<br></div>
mythbackend.20130804041005.**<u></u>1255.log<div class="im"><br>
-rw-rw-r--. 1 mythtv mythtv 8616 Aug 4 00:30<br></div>
mythbackend.20130804042004.**<u></u>1412.log<div class="im"><br>
<br>
Any ideas where to start?<br>
<br>
</div></blockquote><div class="im">
That means your backend is crashing every ten minutes, and something is<br>
automatically restarting it. That last number before ".log" is the process<br>
ID.<br>
<br>
Any idea what that is that keeps connecting to your backend? A frontend<br>
should initially connect as "Playback" rather than "Monitor", and even if<br>
your backend got confused and started connecting back to itself as a slave,<br>
it would show up as "SlaveBackend".<br>
</div></blockquote>
Got me, but I'll start digging. Thanks for giving me a lead!<br>
<br>
</blockquote>
<br>
Yeah. It looks a lot like another case of someone's process monitor, that's set up to ensure MythTV is always running because one assumes MythTV is bound to crash, went haywire and is killing and restarting a perfectly-functional mythbackend. (I still think there are far more cases of the monitors causing problems than of installations of stable versions of MythTV having problems.)<br>
<br>
Mike<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra">Mike:<br><br></div><div class="gmail_extra">You are correct, and sorry for the top-post. I've had a successful process monitor for years, but made a slight tweak before leaving on vacation. Unfortunately, I somehow altered the line to determine if the process is running ("systemctl status mythbackend.service") to match the line for restarting the process. <br>
<br></div><div class="gmail_extra">In defense of process monitors, I run one not because myth is unreliable, but because it is so reliable that it may take several days or more before I notice it isn't running -- by which time I've missed a few of my wife's favorite programs. Since I don't watch TV every night (or sometimes for more than a week, even when home), I can't otherwise monitor the system. Do you have any other suggestions if a process monitor isn't the preferred strategy?<br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">George<br></div></div>