Opened 10 years ago

Closed 10 years ago

#7435 closed defect (invalid)

error opening switch program buffer

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: 0.23
Component: MythTV - General Version: head
Severity: medium Keywords:
Cc: Ticket locked: yes

Description

svn 22595 after a new show on LiveTV it comes "error opening switch program buffer"

Change History (6)

comment:1 Changed 10 years ago by anonymous

svn 22704 after a new show on LiveTV it comes "error opening switch program buffer"

comment:2 Changed 10 years ago by anonymous

I have the same issue with .22 release.

Every time the program changes such as the program boundary in the EPG changing, Live TV always bails out with this error "error opening switch program buffer"

If I pause or rewind live TV around 30 seconds then all is good and live TV will play All day.

comment:3 in reply to:  2 Changed 10 years ago by anonymous

Replying to anonymous:

I have the same issue with .22 release.

Every time the program changes such as the program boundary in the EPG changing, Live TV always bails out with this error "error opening switch program buffer"

If I pause or rewind live TV around 30 seconds then all is good and live TV will play All day.

Update: My frontend and backend are on separate machines. It seems if the clocks on both machines are not in sync this issue raises it head. Even a minute or 2 make a difference. I set up ntp on both machines and now it seems better. Been watching live tv for 6 hours now.

Is it possible that that when the program changes in the EPG that the frontend tries to switch to the new program buffer before the backend has switched program buffers, or the other way around ?

comment:4 Changed 10 years ago by Stuart Auchterlonie

Milestone: 0.22.10.23
Resolution: invalid
Status: newclosed

This is a configuration issue. The backend and frontend machines should always be timesync'd. Otherwise "bad things happen"

comment:5 Changed 10 years ago by anonymous

Resolution: invalid
Status: closednew

Care to elaborate on the required configuration? I am using .22 and have my frontends synced with the backend using ntp and I am still getting this error, often followed by an error stating something like "Cannot connect to master backend. Is it turned on?".

comment:6 Changed 10 years ago by robertm

Resolution: invalid
Status: newclosed
Ticket locked: set

Ask your question on the users list.

Note: See TracTickets for help on using tickets.