[mythtv-users] unstable backend

[Greg Oliver]

On Thu, Apr 20, 2017 at 12:25 PM, Bill Meek <keemllib at gmail.com> wrote:

> On 04/19/2017 07:10 PM, Gabe Rubin wrote:
> ...
>
>
>> https://pastebin.com/Mn5TL6Ws
>>
>
> FYI only:
> Line 64 is commented out, which means Restart is set to the default
> which is "no". Not the cause of this problem, but you could use the
> other options in that file for Restart.
>
> The only logging seems to be the logs that go into /var/log/mythtv/
>>
>
> That's correct (for backend logging) based on line 61 in the paste:
> --logpath /var/log/mythtv.
>
> The logging there seems to be fine, that is how Greg discovered that
>> systemd is killing mythbackend with PID1 (which I am trying to discovery
>> what it is).
>>
>
> Understood. I thought understanding where the backend logging was going
> would be a hint about the journal issue - but no.
>
> ...
>
> When I use the command  journalctl --full --no-pager --unit
>> mythbackend.service I get a ton of logging information, but it ends in
>> October 2016.  Here are the last two lines:
>> Oct 20 08:47:37 Mythbox mythbackend[10381]: 2016-10-20 08:47:37.276062 C
>> Upgrading to MythTV schema version 1327
>> Failed to get journal fields: Bad message
>>
>
> Just Googling for the last line above returns:
>
>     http://forums.fedoraforum.org/showthread.php?s=cc32fbde6f67e
> 1e04015ef46970554d7&p=1769874#post1769874
>
> I've never had the issue, but I'm on *buntu. Use the
> solution at your own risk.
>

Those journal lines are from almost a year ago, so they are probably
irrelevant.  Is there anything relevant in the /var/log/mythbackend* logs
for that time period?  Also, does 'dmesg' show any kernel or process
crashes?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170420/4c003d58/attachment.html>