Guest User

Untitled

a guest
Feb 19th, 2017
81
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.04 KB | None | 0 0
  1. The response to MYTH_PROTO_VERSION was empty.
  2. This happens when the backend is too busy to respond,
  3. or has deadlocked due to bugs or hardware failure.
  4. 2017-02-19 14:37:36.752853 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.1.254:6543 (try 1 of 1)
  5. 2017-02-19 14:37:43.768347 E MythSocket(7f2ac009acd0:57): ReadStringList: Error, timed out after 7000 ms.
  6. 2017-02-19 14:37:43.768502 C Protocol version check failure.
  7. The response to MYTH_PROTO_VERSION was empty.
  8. This happens when the backend is too busy to respond,
  9. or has deadlocked due to bugs or hardware failure.
  10. 2017-02-19 14:37:43.768773 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.1.254:6543 (try 1 of 1)
  11. 2017-02-19 14:37:50.782711 E MythSocket(7f2a9c212f70:57): ReadStringList: Error, timed out after 7000 ms.
  12. 2017-02-19 14:37:50.782862 C Protocol version check failure.
  13. The response to MYTH_PROTO_VERSION was empty.
  14. This happens when the backend is too busy to respond,
  15. or has deadlocked due to bugs or hardware failure.
Add Comment
Please, Sign In to add comment