[mythtv-users] new 0.21 install: cannot record or watch TV

[Greg Woods]

I have a brand-new Fedora 8 install of mythtv-suite 0.21 from ATrpms. I
dumped out the old database and re-sourced it into a completely
different MySQL server. Then to be safe I deleted all capture cards and
set them all up again. But I can't access the capture cards, either
through recording a program or watching live TV. Everything else I've
tried works fine: music, photos, watching existing recordings, guide
data looks good, etc. But I can't record. Here's the backend log from
starting up mythbackend, then trying to watch TV:

2008-03-16 16:55:07.103 Using runtime prefix = /usr, libdir = /usr/lib
2008-03-16 16:55:07.108 Using localhost value of confusion
2008-03-16 16:55:07.121 New DB connection, total: 1
2008-03-16 16:55:07.126 Connected to database 'mythconverg' at host:
192.168.1.1
2
2008-03-16 16:55:07.128 Closing DB connection named 'DBManager0'
2008-03-16 16:55:07.129 Connected to database 'mythconverg' at host:
192.168.1.1
2
2008-03-16 16:55:07.131 New DB connection, total: 2
2008-03-16 16:55:07.133 Connected to database 'mythconverg' at host:
192.168.1.1
2
2008-03-16 16:55:07.136 Current Schema Version: 1214
Running as a slave backend.
2008-03-16 16:55:07.149 HDHRChan(1010051a/0): device found at address
192.168.1.185
2008-03-16 16:55:07.151 New DB connection, total: 3
2008-03-16 16:55:07.152 Connected to database 'mythconverg' at host:
192.168.1.12
2008-03-16 16:55:07.184 HDHRChan(1010051a/1): device found at address
192.168.1.185
2008-03-16 16:55:07.868 Main::Registering HttpStatus Extension
2008-03-16 16:55:07.869 mythbackend version: 0.21.20080304-1
www.mythtv.org
2008-03-16 16:55:07.869 Enabled verbose msgs:  important general
2008-03-16 16:55:08.874 Connecting to master server: 192.168.1.12:6543
2008-03-16 16:55:08.875 Connected successfully
2008-03-16 16:55:38.879 MythSocket(b5307938:14): readStringList: Error,
timeout.
2008-03-16 16:55:38.881 Unknown socket closing
2008-03-16 16:55:38.881 adding: confusion as a slave backend server
2008-03-16 16:55:38.883 MythSocket(b5301d20:-1): writeStringList: Error,
socket went unconnected.
2008-03-16 16:55:38.884 MythSocket(b5303e98:-1): writeStringList: Error,
socket went unconnected.
2008-03-16 16:55:41.779 Unknown socket closing
2008-03-16 16:55:41.787 MythSocket(b5304450:-1): writeStringList: Error,
socket went unconnected.

I searched gossamer-threads and found several other reports of these
socket/stringlist errors, but nothing about how they were solved. 

Anybody have any suggestions as to how I can debug this?

Thanks,
--Greg