somewhere around r25084 (I'm running from -fixes branch), I started seeing the following errors in my master backend:<br><br>2010-08-05 19:33:37.397 MainServer, Warning: Unknown socket closing MythSocket(0xffffffffa9634c38)<br>
2010-08-05 19:33:37.401 MythSocket(ffffffffa9634c38:-1): writeStringList: Error, socket went unconnected.<br> We wrote 0 of 10 bytes with 1 errors<br><br>The backend process doesn't segfault, but nothing can connect or use it either. Sometimes, I get the following errors in the frontend logs:<br>
<br>2010-08-05 19:00:46.554 MythSocket(ffffffffb3a6bd10:35): readStringList: Error, timed out after 30000 ms.<br>2010-08-05 19:00:46.554 Connection to backend server lost<br>2010-08-05 19:00:46.554 MythContext: Connecting to backend server: <a href="http://192.168.1.3:6543">192.168.1.3:6543</a> (try 1 of 1)<br>
2010-08-05 19:00:53.554 MythSocket(ffffffffa4b00c98:35): readStringList: Error, timed out after 7000 ms.<br>2010-08-05 19:00:53.554 Protocol version check failure.<br> The response to MYTH_PROTO_VERSION was empty.<br>
This happens when the backend is too busy to respond,<br> or has deadlocked in due to bugs or hardware failure.<br>2010-08-05 19:00:53.554 Reconnection to backend server failed<br>
<br>Anyone else experiencing this? Have a workaround or fix?<br><br>