So I upgraded mythtv last night to latest git pull.<div><br></div><div><div>MythTV Version : v0.25pre-2003-gfd5e33a</div><div>MythTV Branch : master</div><div>Network Protocol : 65</div><div>Library API : 0.25.20110429-1</div>
<div>QT Version : 4.6.3</div></div><div><br></div><div>I started up mythbackend... seems to be fine. When I run the frontend it complains that it cannot communicate to the backend.</div><div><br></div><div><div>2011-05-19 06:54:58.709 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:54:58.709 MythSocket(ffffffffa8fd7c50:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:54:58.710 MythSocket(ffffffffa8fd7c50:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:54:58.710 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div><div>2011-05-19 06:55:03.712 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:55:03.713 MythSocket(ffffffffad76bdf8:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:55:03.713 MythSocket(ffffffffad76bdf8:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:55:03.714 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div><div>2011-05-19 06:55:08.714 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:55:08.715 MythSocket(ffffffffa8005008:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:55:08.716 MythSocket(ffffffffa8005008:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:55:08.716 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div><div>2011-05-19 06:55:13.201 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:55:13.203 MythSocket(933ab80:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:55:13.203 MythSocket(933ab80:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:55:13.204 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div><div>2011-05-19 06:55:13.716 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:55:13.718 MythSocket(ffffffffa8ff4348:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:55:13.718 MythSocket(ffffffffa8ff4348:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:55:13.718 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div><div>2011-05-19 06:55:15.129 MythCoreContext: Connecting to backend server: <a href="http://192.168.0.10:6543">192.168.0.10:6543</a> (try 1 of 1)</div>
<div>2011-05-19 06:55:15.130 MythSocket(955aa68:-1): writeStringList: Error, writeBlock failed. (UnknownError)</div><div>2011-05-19 06:55:15.130 MythSocket(955aa68:-1): readStringList: Error, called with unconnected socket.</div>
<div>2011-05-19 06:55:15.131 Protocol version check failure.</div><div> The response to MYTH_PROTO_VERSION was empty.</div><div> This happens when the backend is too busy to respond,</div>
<div> or has deadlocked in due to bugs or hardware failure.</div></div><div><br></div><div>This happens on the backend machine and on remote machines. Also, trying to bring up mythweb I see this error:</div>
<div><br></div><div><div>Unable to connect to the master backend at <a href="http://192.168.0.10:6543">192.168.0.10:6543</a>.</div><div>Is it running?</div></div><div><br></div><div>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?</div>
<div><br></div><div>Thanks,</div><div>-Greg</div>