[mythtv-users] Shows Chopped Up and Long Queue of Comm Flag / Metadata Jobs

[Michael T. Dean]

fixed top-posting


On 08/05/2013 04:17 PM, George Galt wrote:
> On Mon, Aug 5, 2013 at 4:15 PM, Raymond Wagner wrote:
>
>> On 8/5/2013 4:09 PM, George Galt wrote:
>>
>>> and I'm getting new logs every 10 minutes:
>>> -rw-rw-r--. 1 mythtv mythtv  12782 Aug  4 00:00
>>> mythbackend.20130804035006.**890.log
>>> -rw-rw-r--. 1 mythtv mythtv   8616 Aug  4 00:10
>>> mythbackend.20130804040009.**1065.log
>>> -rw-rw-r--. 1 mythtv mythtv   9707 Aug  4 00:20
>>> mythbackend.20130804041005.**1255.log
>>> -rw-rw-r--. 1 mythtv mythtv   8616 Aug  4 00:30
>>> mythbackend.20130804042004.**1412.log
>>>
>>> Any ideas where to start?
>>>
>> That means your backend is crashing every ten minutes, and something is
>> automatically restarting it.  That last number before ".log" is the process
>> ID.
>>
>> Any idea what that is that keeps connecting to your backend?  A frontend
>> should initially connect as "Playback" rather than "Monitor", and even if
>> your backend got confused and started connecting back to itself as a slave,
>> it would show up as "SlaveBackend".
> Got me, but I'll start digging.  Thanks for giving me a lead!
>

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.)

Mike