[mythtv-users] unstable backend

[Gabe Rubin]

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

> On 04/19/2017 01:53 PM, Gabe Rubin wrote:
>
>> On Wed, Apr 19, 2017 at 11:18 AM, Greg Oliver <oliver.greg at gmail.com>
>> wrote:
>>
>> On Wed, Apr 19, 2017 at 12:35 PM, Gabe Rubin <gaberubin at gmail.com> wrote:
>>>
>>> Lately, my backend has been fairly unstable, with the frontend taking
>>>> quite some time to display my recordings (basically seems like it has to
>>>> restart the backend) and mythweb not displaying any recordings in the
>>>> Recorded Programs section, even after a backend restart.  I have to
>>>> restart
>>>> the whole system (a combined FE/BE).  I am running version:
>>>> mythtv-backend-0.28-12
>>>>
>>>> I can post my full log from the backend, but this seems like the
>>>> relevant
>>>> portion (the last part of the log):
>>>>
>>>> 2017-04-19 10:02:38.686676 I [26528/16485] MythSocketThread(78)
>>>> mainserver.cpp:7656 (connectionClosed) - Monitor sock(de1090) 'Mythbox'
>>>> disconnected
>>>> 2017-04-19 10:05:26.116680 C [26528/26528] CoreContext
>>>> signalhandling.cpp:305 (handleSignal) - Received Terminated: Code 0,
>>>> PID 1,
>>>> UID 0, Value 0x00000000
>>>> 2017-04-19 10:05:26.117772 N [26528/26528] CoreContext
>>>> main_helpers.cpp:730 (run_backend) - MythBackend exiting
>>>>
>>>>
>>>>
>>>> Looks like it is being killed by PID1 - which is init or systemd
>>> depending
>>> on your system.  You should have system logs or journal that tells you
>>> why
>>> it is happening.  journalctl or files in /var/log/
>>>
>>>
>>>
>>> I am running fedora, so using systemd.  Where would I find the logs in
>> /var/log/ (/var/log/journal/ has a directory named
>> 19a3360c5cac4dd7abd27b7d5b9aac98 and there does not seem to be readable
>> files in it)?  When I use the journalctl command, i have to constantly
>> space to get the next page of data.  It cuts out at April 5, with this as
>> the last message (making me think there is some other issue going on):
>>
>>
>> Apr 05 19:24:20 Mythbox /usr/libexec/gdm-x-session[1532]: (--)
>> NVIDIA(GPU-0): ONKYO Corporation TX-NR525 (DFP-2): connected
>> Failed to get journal fields: Bad message
>>
>
> journalctl has lots-o-options, but try this:
>
>     journalctl --full --no-pager --unit mythtv-backend
>
> Not sure about the April 5th comment. I'd look at the logging that
> the backend is started with first:
>
>     systemctl cat mythtv-backend
>
> This may be of interest:
>
>     grep ForwardToSyslog /etc/systemd/journald.conf
>
> --
> Bill
>
>
These are the respective results:

[root at Mythbox 19a3360c5cac4dd7abd27b7d5b9aac98]#  journalctl --full
--no-pager --unit mythtv-backend
-- No entries --
[root at Mythbox 19a3360c5cac4dd7abd27b7d5b9aac98]# grep ForwardToSyslog
/etc/systemd/journald.conf
#ForwardToSyslog=no
[root at Mythbox 19a3360c5cac4dd7abd27b7d5b9aac98]# systemctl cat
mythtv-backend
No files found for mythtv-backend.service.
[root at Mythbox 19a3360c5cac4dd7abd27b7d5b9aac98]#
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170419/99dc99b3/attachment.html>