Advertisement
Guest User

Untitled

a guest
Nov 20th, 2013
149
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.52 KB | None | 0 0
  1. 2013-11-20 19:31:46.030420 I MythCoreContext: Connecting to backend server: 10.1.0.5:6543 (try 1 of 1)
  2. 2013-11-20 19:31:53.075630 E MythSocket(a0c100:23): ReadStringList: Error, timed out after 7000 ms.
  3. 2013-11-20 19:31:53.075906 C Protocol version check failure.
  4. The response to MYTH_PROTO_VERSION was empty.
  5. This happens when the backend is too busy to respond,
  6. or has deadlocked due to bugs or hardware failure.
  7. 2013-11-20 19:31:53.076227 E Error rescheduling MATCH 0 0 0 - MythFillDatabase in ScheduledRecording::SendReschedule
  8. 2013-11-20 19:31:53.076655 N mythfilldatabase run complete.
  9. 2013-11-20 19:31:53.076866 I MythCoreContext: Connecting to backend server: 10.1.0.5:6543 (try 1 of 1)
  10. 2013-11-20 19:31:53.077304 I Waiting for threads to exit.
  11. 2013-11-20 19:32:00.121173 E MythSocket(7fde6400b860:25): ReadStringList: Error, timed out after 7000 ms.
  12. 2013-11-20 19:32:00.121440 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.
  16. 2013-11-20 19:32:00.121953 I MythCoreContext: Connecting to backend server: 10.1.0.5:6543 (try 1 of 1)
  17. 2013-11-20 19:32:07.165491 E MythSocket(7fde5000b880:25): ReadStringList: Error, timed out after 7000 ms.
  18. 2013-11-20 19:32:07.165762 C Protocol version check failure.
  19. The response to MYTH_PROTO_VERSION was empty.
  20. This happens when the backend is too busy to respond,
  21. or has deadlocked due to bugs or hardware failure.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement