[mythtv-users] Just upgraded to latest git and now I get "Protocol version check failure."

[Greg Grotsky]

So I upgraded mythtv last night to latest git pull.

MythTV Version   : v0.25pre-2003-gfd5e33a
MythTV Branch    : master
Network Protocol : 65
Library API      : 0.25.20110429-1
QT Version       : 4.6.3

I started up mythbackend... seems to be fine.  When I run the frontend it
complains that it cannot communicate to the backend.

2011-05-19 06:54:58.709 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:54:58.709 MythSocket(ffffffffa8fd7c50:-1): writeStringList:
Error, writeBlock failed. (UnknownError)
2011-05-19 06:54:58.710 MythSocket(ffffffffa8fd7c50:-1): readStringList:
Error, called with unconnected socket.
2011-05-19 06:54:58.710 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.
2011-05-19 06:55:03.712 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:55:03.713 MythSocket(ffffffffad76bdf8:-1): writeStringList:
Error, writeBlock failed. (UnknownError)
2011-05-19 06:55:03.713 MythSocket(ffffffffad76bdf8:-1): readStringList:
Error, called with unconnected socket.
2011-05-19 06:55:03.714 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.
2011-05-19 06:55:08.714 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:55:08.715 MythSocket(ffffffffa8005008:-1): writeStringList:
Error, writeBlock failed. (UnknownError)
2011-05-19 06:55:08.716 MythSocket(ffffffffa8005008:-1): readStringList:
Error, called with unconnected socket.
2011-05-19 06:55:08.716 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.
2011-05-19 06:55:13.201 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:55:13.203 MythSocket(933ab80:-1): writeStringList: Error,
writeBlock failed. (UnknownError)
2011-05-19 06:55:13.203 MythSocket(933ab80:-1): readStringList: Error,
called with unconnected socket.
2011-05-19 06:55:13.204 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.
2011-05-19 06:55:13.716 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:55:13.718 MythSocket(ffffffffa8ff4348:-1): writeStringList:
Error, writeBlock failed. (UnknownError)
2011-05-19 06:55:13.718 MythSocket(ffffffffa8ff4348:-1): readStringList:
Error, called with unconnected socket.
2011-05-19 06:55:13.718 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.
2011-05-19 06:55:15.129 MythCoreContext: Connecting to backend server:
192.168.0.10:6543 (try 1 of 1)
2011-05-19 06:55:15.130 MythSocket(955aa68:-1): writeStringList: Error,
writeBlock failed. (UnknownError)
2011-05-19 06:55:15.130 MythSocket(955aa68:-1): readStringList: Error,
called with unconnected socket.
2011-05-19 06:55:15.131 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.

This happens on the backend machine and on remote machines.  Also, trying to
bring up mythweb I see this error:

Unable to connect to the master backend at 192.168.0.10:6543.
Is it running?

192.168.0.10 is the IP address of my backend server.  Not sure how to fix
this, as I haven't changed anything configuration-wise, and I don't want to
muck anything up further... anyone know what's going on here or how to fix
it?

Thanks,
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110519/b6cc32fe/attachment.html