[mythtv-users] unstable backend

[Bill Meek]

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.

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

-- 
Bill