<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 7/20/19 6:30 PM, R Kannan wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0a4c9bda-6e4d-9772-b465-4a1bea7418c4@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 7/20/19 8:38 AM, R Kannan wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e4a27860-3e2e-05f3-8b8e-d82af7a48fb4@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">On 7/20/19 8:00 AM, <a
class="moz-txt-link-abbreviated"
href="mailto:mythtv-users-request@mythtv.org"
moz-do-not-send="true">mythtv-users-request@mythtv.org</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.3.1563624002.12859.mythtv-users@mythtv.org">
<pre class="moz-quote-pre" wrap="">On Sat, 20 Jul 2019 09:37:03 +0100, you wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">On 20/07/2019 09:15, Stephen Worthington wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">If this is your first network tuner, you may not have done the fix for
getting mythbackend to start up only after the network is actually
available. So every time you reboot, mythbackend will not see the
network tuner as it starts when only localhost is up. If it is unable
to test a tuner at startup, it marks it as bad and does not use it. To
test if this is your problem, just restart mythbackend, and as the
network is up now, it will see the network tuners and everything will
work unitl the next reboot.
If you need that fix, see my post on the recent "Need mythtv-backend
startup advice" thread.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">This is getting old. Is anyone going to fix the backend systemd service file so that it does the
right thing - wait for the ACTUAL network to be up, not just localhost?
That way, we won't keep getting puzzled calls from users whose systems can't find network tuners, etc.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">There are plenty of users who do not need the full network to be up -
they do not have network tuners and are running just a combined
backend/frontend. For them, localhost is all they need. The
Mythbuntu install package already asks if you are going to need
outside access for frontends, or something like that, if I remember
correctly. It should change the question to make it clear that
network tuners are included, and when the answer to that question is
that the network is needed, it should install the proper systemd
setup. Anyone adding network tuners later would then only need to run
dpkg-reconfigure and change their answer to that question.
</pre>
</blockquote>
<p>Perhaps I did not make it clear enough. Immediately after I
installed the tuner (which a replaced an broken HDHR) MythTV
was working fine three weeks back. I tried Live TV after a
recording was missed and found that MythTV was unabled to tune
into HDHR.</p>
<p>Also note that HDHR Config GUI on this box and another device
on the network was able to tune into OTR channels fine.<br>
</p>
</blockquote>
<p>Rebooted the box and everything is fine now.<br>
</p>
</blockquote>
<p>BTW. I think it may be something to do with MythBackend starting
before the HDHR tuner is up and running. Restarting the backend
does not fix this issue.</p>
<p> There was a power failure after my fix above (welcome
thunderstorm after the heat wave here in MI) and both my
MythBackend box and the HDHR were rebooted. The backend could
not tune into the card again. I had to reboot to get that working.<br>
</p>
</body>
</html>