[mythtv-users] unstable backend

[Gabe Rubin]

On Wed, Apr 19, 2017 at 1:05 PM, Bill Meek <keemllib at gmail.com> wrote:

> On 04/19/2017 02:34 PM, Gabe Rubin wrote:
>
>> On Wed, Apr 19, 2017 at 12:29 PM, Bill Meek <keemllib at gmail.com> wrote:
>>
>> On 04/19/2017 02:17 PM, Gabe Rubin wrote:
>>>
>>> These are the respective results:
>>>
>>>>
>>>> ...
>>>
>>> # systemctl cat mythtv-backend
>>>> No files found for mythtv-backend.service.
>>>> [root at Mythbox 19a3360c5cac4dd7abd27b7d5b9aac98]#
>>>>
>>>>
>>> Maybe Fedora uses a different name for the backend service.
>>>
>>> Try pressing the tab key after: systemctl cat my
>>>
>>>
>>> That worked, cat mythbackend.service
>>
>>
>> Should I paste the output?
>>
>
> Sure, at pastebin.com (or your favorite.) But the key is what
> type of logging is being used when the backend is started. E.g
> --syslog localX or --logpath /some/path/name
>
> Then verify the permissions: ls -ld /var/log/mythtv (or if the
> above has a different logpath, use it.
>

https://pastebin.com/Mn5TL6Ws

The only logging seems to be the logs that go into /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).



>
> I did this also:
>> ... #  journalctl --full--no-pager --unit myth
>> -- No entries --
>>
>
> If you really typed --unit myth, then retry with myth<tab>, or just
> mythbackend
> otherwise, the backend isn't logging to the journal.
>
> Then you can use journalctl --no-pager --full --until <timestamp> where
> timestamp is from
> the backend exiting. Look for other things that may be going on at the
> time e.g. a cron
> job used to restart the backend etc.
>
>
>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170419/4623906c/attachment.html>