[mythtv-users] "Error opening jump program file" when switching tuners: is this a known problem and did I really fix it?

Anthony Rooney rooneyo at iinet.net.au
Thu Sep 16 10:11:37 UTC 2010


Hi Michael

Thanks for your feedback.

Elements of your comments are unclear.

You wrote " MythTV cannot read from the file that contains the video" & "
That's more likely a socket-related issue that's causing the frontend to
fail to read the recording data"  I am trying to run Live TV not read an
existing  recording.  Are you saying when a network client runs Live TV it
does not stream video over the wire but it reads data from the backend
server HD or from memory on the backend system?

I am curious how I could develop a socket issue across a network that
previously work fine.  I presume something has changed within the backend
system as it is unlikely that BOTH client machines changed simultaneously.

I will check the logs.  Can you advise which logs on which machine I presume
the backend system?

Many Thanks


Anthony



-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Michael T. Dean
Sent: Thursday, 16 September 2010 3:13 AM
To: Discussion about MythTV
Subject: Re: [mythtv-users] "Error opening jump program file" when switching
tuners: is this a known problem and did I really fix it?

  On 09/15/2010 09:07 AM, Anthony Rooney wrote:
> I get the "Error opening jump program file" when I try to run Live Tv 
> to connect to the backend system which has the tuner attached.  If I 
> go to the Backend system and run the front end application and connect 
> to a known good channel it all works fine and I can change channels 
> OK.  If I go to one of either of the other client systems on the 
> network I briefly see the channel information for half a second before 
> getting the "Error opening jump program file".  I cannot understand 
> the significance of the 1st channel setting in the backend as it seems 
> to be only the last channel set when MythTv  was last used on this system.

It's a completely useless setting (scheduled for removal) that ensures that
the first time you ever use your MythTV system after first configuring your
video sources, capture cards, and input connections, MythTV tries to tune a
good channel.

>    I read somewhere to make sure the 1st channel was set to 3?

It can be set to anything, as long as it's a valid channel in the source.

> What on earth does this error "Error opening jump program file" mean

That MythTV cannot read from the file that contains the video.

>   and why
> is it so debilitating to completely stop both client machines which 
> previously worked fine from ever running Live TV.  I cannot get any 
> advice or assistance to troubleshoot this error yet it has completely 
> broken the client server functionality.

That's more likely a socket-related issue that's causing the frontend to
fail to read the recording data, and the backend's network code to die.  
Check your logs for socket-related errors.  That said, if it is
socket-related issues, I don't know how to help you fix them (if I--or any
of the developers--did, we'd just fix the MythTV socket-related code).

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



More information about the mythtv-users mailing list