[mythtv-users] Can't get to "Watch Recordings" screen

Brian Phillips brian.phillips at gmx.net
Mon Nov 8 04:45:35 UTC 2010


Hello,

I'm still running mythbuntu 8.04, MythTV 0.21.  I have a master backend on a
headless machine with a single remote frontend.

Within the last week, I lost the ability to enter the "Watch Recordings"
screen.  The frontend accesses the database completely in other respects
(Mythvideo functions correctly, all settings are correct, etc) but when I
got to "Watch Recordings" the frontend hangs and either killed or the
backend can be restarted, at which point the frontend asks me if the backend
is running and if I know the correct IP address.  I can then go back to the
main menu and try again, but get the same result.

I've truncated the "recorded" table and been able to successfully enter the
"watch recordings" screen.

I tried to delete the most recent 2 weeks of "recorded" data from the
database, but still can't get to the "watch recordings" screen.  I have 720
rows in the "recorded" table, and I wasn't able to enter the "Watch
Recordings" screen until I had deleted about 700 of those rows!

I can see all the recorded programs on Mythweb's "Recorded Programs" page.

I've tried logging the frontend and backend with "--verbose all" and the
backend gives me a little too much information to process, the frontend
tells me:

============================
2010-11-07 21:18:29.423 Connecting to backend server: 192.168.0.101:6543
(try 1 of 5)
2010-11-07 21:18:29.423 MythSocket(835d9d8:15): new socket
2010-11-07 21:18:29.424 MythSocket(835d9d8:15): attempting connect() to
(192.168.0.101:6543)
2010-11-07 21:18:29.424 MythSocket(835d9d8:15): state change Idle ->
Connected
2010-11-07 21:18:29.424 write -> 15 21      MYTH_PROTO_VERSION 40
2010-11-07 21:18:29.442 read  <- 15 13      ACCEPT[]:[]40
2010-11-07 21:18:29.442 Using protocol version 40
2010-11-07 21:18:29.442 write -> 15 17      ANN Monitor atv 0
2010-11-07 21:18:29.452 read  <- 15 2       OK
2010-11-07 21:18:29.452 MythSocket(841dde0:14): attempting connect() to
(192.168.0.101:6543)
2010-11-07 21:18:29.452 MythSocket(841dde0:14): state change Idle ->
Connected
2010-11-07 21:18:29.452 write -> 14 17      ANN Monitor atv 1
2010-11-07 21:18:29.473 read  <- 14 2       OK
2010-11-07 21:18:29.473 MythSocket: readyread thread start
2010-11-07 21:18:29.473 MythSocket(841dde0:14): UpRef: 1
2010-11-07 21:18:29.473 write -> 15 21      QUERY_RECORDINGS Play
============================

I wish I could isolate the reason for why the frontend won't display the
"Watch Recordings" screen.  I'd hate to lose all my "recorded" shows, but
it's looking like either that or going through each entry, testing, and then
isolating the one (or multiple ones) that are causing the freeze.

One key "hiccup" that was abnormal: the backend was not scheduling the
"mythfilldatabase" correctly.  And I had run out of guide data recently.
Some of the shows that were recently recorded and had incorrect plot
synposis which are usually placeholders in SchedulesDirect data.  The
placeholders are usually overwritten and corrected when the show is about
10-13 days from airdate.  I believe this is probably the key, but like I
said, I deleted the last year of data from the "recorded" table, but still
could not enter "Watch Recordings".  It wasn't until I had deleted about 2
years worth of "recorded" entries that I was able to get to "Watch
Recordings".

Help me mythtv-users list...

Brian





More information about the mythtv-users mailing list