On Tue, Sep 11, 2012 at 12:29 AM, David Whyte <span dir="ltr"><<a href="mailto:david.whyte@gmail.com" target="_blank">david.whyte@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
My mythTV setup includes a couple of HDHomeRun tuners. They are<br>
generally flawless in their operation, providing all channels and<br>
never skipping a beat...until recently.<br>
<br>
A couple of weeks ago, I applied all security updates to my BE,<br>
including a mythbuntu packaged mythTV update and a new kernel and did<br>
a reboot. Everything seemed fine until I noticed later that week that<br>
all of the subsequent recordings resulted in a zero byte file. I<br>
checked the tuners were working, using the HDHomeRun Config GUI tool<br>
and viewing streams on all of the tuners. I applied a further mythTV<br>
update (not requiring a reboot) and everything came good. Despite<br>
Google, trac and mailing list searches turning up nothing, I blamed<br>
the bug on mythTV and decided it had been resolved in the second<br>
update.<br>
<br>
Last night I also did a hardware upgrade to the BE machine, requiring<br>
it to be shutdown. Since it was being shutdown, I decided to apply<br>
all new updates, including a new kernel, but elected *not* to update<br>
the mythTV packages from mythbuntu. Afterwards, I noticed that some<br>
of the nights recordings from just one of the HDHomeRuns had resulted<br>
in zero byte files. A quick look at the HDHome Config GUI showed that<br>
all the tuners were capable of tuning and displaying a program. I<br>
then restarted the backend and it seemed that all tuners were again<br>
working fine.<br>
<br>
On both occasions, one (or both) actions of using the HDHomeRun Config<br>
GUI or restarting the BE resulted in everything coming good.<br>
<br>
Some pertinent information:<br>
- MythTV is configured to use the HDHomeRun tuners via their device ID.<br>
- My BE is also the DHCP server in the network, and it assigns static<br>
IPs to the HDHomeRuns. (My modem also acts as a DHCP server and it is<br>
a bit of a race condition as to which DHCP server responds when a DHCP<br>
lease is required though investigations have shown that the BE is much<br>
more likely to respond to DHCP requests).<br></blockquote><div><br></div><div>Why the heck would you have two DHCP servers on your network? Solve this problem first. </div><div><br></div><div>I remember mythtv didn't play nice when the HDHR IP address changes while mythbackend is still running. My situation was that mythbackend started up prior to the HDHR obtaining a DHCP, so strangeness would happen. I had to modify the init scripts to wait for the HDHR networking to stabilize before mythbackend starting. However, this was several months back using 0.24. I am not sure if any recent changes went into this area.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- The mythbackend logs show the failed recordings with logs similar to<br>
the following (note the HDHomeRun device ID of 1110625E-0):<br>
<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: I TVRecEvent<br>
tv_rec.cpp:1029 (HandleStateChange) TVRec(19): Changing from None to<br>
RecordingOnly<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: I TVRecEvent<br>
tv_rec.cpp:3495 (TuningCheckForHWChange) TVRec(19): HW Tuner: 19->19<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: E TVRecEvent<br>
dtvmultiplex.cpp:325 (ParseTuningParams) DTVMux: ParseTuningParams --<br>
Unknown tuner type = 0xffffffff80000000<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: E TVRecEvent<br>
dtvchannel.cpp:308 (SetChannelByString) DTVChan(1110625E-0):<br>
SetChannelByString(2): Failed to initialize multiplex options<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: E TVRecEvent<br>
tv_rec.cpp:3681 (TuningFrequency) TVRec(19): Failed to set channel to<br>
2. Reverting to kState_None<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: I TVRecEvent<br>
tv_rec.cpp:1029 (HandleStateChange) TVRec(19): Changing from<br>
RecordingOnly to None<br>
Sep 10 22:53:51 mythBE1 mythbackend[1545]: I CoreContext<br>
scheduler.cpp:637 (UpdateRecStatus) Updating status for Lateline on<br>
cardid 19 (Will Record => Recorder Failed)<br>
<br>
<br>
Does anybody have any ideas as to what is going on here? Is it<br>
possible mythTV is not correctly finding the HDHomeRun at startup and<br>
never corrects itself? Or does it find the HDHomeRun somehow, but at<br>
that point in time, the HDHomeRun has been assigned an IP from the<br>
modem and when it gets a subsequent lease from the BE's DHCP server<br>
mythTV's reference to it is wrong?<br>
<br>
Thanks in advance,<br>
Whytey<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br>