[mythtv-users] Starting mythfrontend with systemd?
dheianevans at gmail.com
Fri Oct 6 05:56:02 UTC 2017
On Fri, Oct 6, 2017 at 12:53 AM, Ian Evans <dheianevans at gmail.com> wrote:
> On Thu, Oct 5, 2017 at 11:35 PM, Ian Evans <dheianevans at gmail.com> wrote:
>> On Thu, Oct 5, 2017 at 10:54 PM, Bill Meek <keemllib at gmail.com> wrote:
>>> On 10/05/2017 09:49 PM, Ian Evans wrote:
>>>> Your version of the systemd file worked, well, the first time The
>>>> "Attempting to connect" came up briefly, the progress bar got about a
>>>> of the way across and then the menu screem.
>>>> Waited a few minutes and rebooted to see if it would start again. This
>>>> the progress bar went all the way across and failed.
>>> Did you change/add the Type=notify line in mythtv-backend.service and do
>> Yes to the type=notify,
>> By daemon-reload do you mean I have to do the systemctl enable? Or does
>> rebooting (which I did) do the daemon-reload?
> After Googling the systemd daemon reload, I did that. So with the only
> addition to my backend service being Type=notify, the backend (which was
> working fine) now seems to be going crazy.
> The frontend loads and then every few minutes tosses a lost connection
> mythcontext message. So, like right now I'm recording Seth Myers and so far
> it's about 6 different files as the backend keeps failing. A lot of
> connection closed messages in the mythbackend log.
Okay. So all I did about half an hour ago was remove the Type=notify in the
backend service file. Daemon reload. Restart service.
Now the recordings are working fine again. I do not get this. Nice
forehead-shaped dent in my desk.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users