[mythtv-users] 0.25 - livetv fails when starting on a specificchannel

[Michael T. Dean]

On 03/18/2012 08:00 PM, Scott & Nicole Harris wrote:
>>> I'm running 0.25 from about a week ago. Today I discovered a case
>>> where livetv consistently won't work if I start on a particular
>>> channel. If I start on another channel and switch to that channel, it
>>> works fine. However if I start on that channel it hangs for about 10
>>> seconds before dumping back to the menu with the "error opening
>>> jumpfile" message. However, I've noticed that even though it doesn't
>>> playback, the 10 second file is created, and if I go into the
>>> "recorded programs" screen and switch to the livetv group, the
>>> recording is there and it plays fine. I also did some testing with
>>> mplayer, where as soon as I start mythtv in livetv and it's waiting
>>> for the video to start, I quickly switch to mplayer and begin to play
>>> the mpg file, and the file works fine. So it's not a case where the
>>> data isn't making into the file (or the data isn't being flushed) in a
>>> timely manner, because mplayer is seeing it just fine at the same time
>>> that myth can't.
>> I did some more debugging on this. Turning off the AlwaysStreamFiles
>> setting files seems to let playback work on this channel. I couldn't
>> find that setting in the setup screens (was it removed in 0.25?) so I
>> just disabled in the database and that took care of it. Still don't
>> know why it's just that one channel that fails for streaming. Any
>> ideas?
> That's interesting.  I have one FE that will not play live TV without
> AlwaysStreamFiles turned ON (it just hangs at a blank screen for ~10
> seconds, then the "error opening jumpfile") and have never figured out why.

Almost definitely NFS misconfiguration, as Daniel mentioned.  
http://www.mythtv.org/docs/mythtv-HOWTO-23.html#ss23.8 (specifically the 
actimeo option).

> About the only thing I can think of is this FE is also a SBE (though that is
> now turned off in favor of mythjobqueue) and it has identical folders
> mounted to the the MBE to allow it to do transcodes.  Maybe something to do
> with that?
>
> It's also a little concerning that the setting itself has been removed from
> Myth settings screens (I believe it was gone in 0.24 too,but don't quote me
> on that), but it still seems to have a pretty big impact.

The setting was removed because it's a broken setting that was used to 
work around system misconfiguration.

If you want mythbackend to stream files, you should ensure the file 
system on which those files exist is not mounted locally.  If you want 
mythfrontend to read files "locally", you should ensure the file system 
on which those files exist is mounted locally.

Or, put another way, if you want to use NFS, use NFS.  If not, don't.

There is absolutely no reason to mount a file system locally using NFS 
if you don't have mythfrontend reading files for playback over NFS.

If you think there's a reason, then there's some other problem with your 
configuration that you're not fixing that make you think so.  And, when 
fixed, your system will work properly without having to force a value 
for the setting.

Mike