I'm having issues with anything accessing mythbackend, and I hope someone here might know what's going on. Everything seems to work fine until it attempt to record something. I can set up a recording, and the computer wakes up and the USB tuner shows a blue light, which means it's tuned in. Nothing gets recorded and any attempt to access the backend fails. Nothing seems to be using significant amounts of CPU time.
Using the frontend from a remote computer shows a lot of messages like this, once I select the "recorded programs" function:
In Mythweb, if I try to access the list of recorded programs or the TV guide, I see messages in the browser like this:
2013-01-06 13:21:49.354303 I MythCoreContext: Connecting to backend server: 192.168.181.3:6543 (try 1 of 1)
2013-01-06 13:21:56.358295 E MythSocket(3100d60:40): readStringList: Error, timed out after 7000 ms.
2013-01-06 13:21:56.358403 C Protocol version check failure.
The response to MYTH_PROTO_VERSION was empty.
This happens when the backend is too busy to respond,
or has deadlocked in due to bugs or hardware failure.
I've tried reinstalling a few times, and I don't think I've done anything stupid but I wouldn't be surprised. I've attached various logs, debug traces and package information. I don't see anything obvious in syslog. I notice that there's various error messages about accessing the database, yet I can access it from the mysql client fine. I didn't have this problem with Mythbuntu versions older than 12.04. Does anyone know what's going on?
User Notice at /usr/share/mythtv/bindings/php/MythBackend.php, line 105:
!!NoTrans: Unexpected response to MYTH_PROTO_VERSION '72': !!