Ticket #9274: mythfrontend.log

File mythfrontend.log, 44.3 KB (added by brian@…, 13 years ago)

frontend log: incident #2

Line 
12010-12-19 22:48:37.037 mythfrontend version: branches/release-0-24-fixes [27334] www.mythtv.org
22010-12-19 22:48:37.037 Using runtime prefix = /usr
32010-12-19 22:48:37.037 Using configuration directory = /home/jennifer/.mythtv
42010-12-19 22:48:37.038 ThreadPool:HTTP: Initial 1, Max 25, Timeout 60000
52010-12-19 22:48:37.537 Setting 'RunFrontendInWindow' being forced to '0'
62010-12-19 22:48:37.537 Using localhost value of jenny
72010-12-19 22:48:37.652 New DB connection, total: 1
82010-12-19 22:48:37.670 Connected to database 'mythconverg' at host: pvr
92010-12-19 22:48:37.718 Closing DB connection named 'DBManager0'
102010-12-19 22:48:37.720 Connected to database 'mythconverg' at host: pvr
112010-12-19 22:48:37.732 Current locale EN_CA
122010-12-19 22:48:37.733 Reading locale defaults from /usr/share/mythtv//locales/en_ca.xml
132010-12-19 22:48:37.941 ScreenSaverX11Private: Gnome screen saver support enabled
142010-12-19 22:48:37.942 DPMS is disabled.
152010-12-19 22:48:37.973 Desktop video mode: 1280x720 59.943 Hz
162010-12-19 22:48:38.016 Enabled verbose msgs:  important general
172010-12-19 22:48:38.024 Loading en_us translation for module mythfrontend
182010-12-19 22:48:38.027 Desktop video mode: 1280x720 59.943 Hz
192010-12-19 22:48:38.044 Trying 1280x720 0.000 Hz
202010-12-19 22:48:38.214 SwitchToGUI: Switched to 1280x720 0.000 Hz
212010-12-19 22:48:38.227 LIRC: Successfully initialized '/dev/lircd' using '/home/jennifer/.mythtv/lircrc' config
222010-12-19 22:48:38.227 JoystickMenuThread: Joystick disabled - Failed to read /home/jennifer/.mythtv/joystickmenurc
232010-12-19 22:48:38.330 Using Frameless Window
242010-12-19 22:48:38.331 Using Full Screen Window
252010-12-19 22:48:38.442 Using the OpenGL painter
262010-12-19 22:48:38.519 OpenGL: OpenGL vendor  : NVIDIA Corporation
272010-12-19 22:48:38.520 OpenGL: OpenGL renderer: GeForce 8400 GS/PCI/SSE2/3DNOW!
282010-12-19 22:48:38.520 OpenGL: OpenGL version : 3.3.0 NVIDIA 260.19.06
292010-12-19 22:48:38.520 OpenGL: Max texture size: 8192 x 8192
302010-12-19 22:48:38.520 OpenGL: Max texture units: 4
312010-12-19 22:48:38.520 OpenGL: Direct rendering: Yes
322010-12-19 22:48:38.520 OpenGL: Initialised MythRenderOpenGL
332010-12-19 22:48:38.520 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720
342010-12-19 22:48:38.524 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720/bkg
352010-12-19 22:48:38.525 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720/keyboard
362010-12-19 22:48:38.528 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720/title
372010-12-19 22:48:38.529 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720/type
382010-12-19 22:48:38.529 Removing stale cache dir: /home/jennifer/.mythtv/themecache/G.A.N.T.1280.720/watermark
392010-12-19 22:48:38.870 Current MythTV Schema Version (DBSchemaVer): 1264
402010-12-19 22:48:38.880 New DB connection, total: 2
412010-12-19 22:48:38.886 Connected to database 'mythconverg' at host: pvr
422010-12-19 22:48:39.222 ThemeInfo, Warning: Unable to open themeinfo.xml for /usr/share/mythtv/themes/BlackCurves-OSD/themeinfo.xml
432010-12-19 22:48:39.222 ThemeInfo, Error: The theme (/usr/share/mythtv/themes/BlackCurves-OSD) is missing a themeinfo.xml file.
442010-12-19 22:48:39.223 ThemeInfo, Error: Unable to parse themeinfo.xml for /usr/share/mythtv/themes/glass-wide/themeinfo.xml
452010-12-19 22:48:39.223 ThemeInfo, Error: The theme (/usr/share/mythtv/themes/glass-wide) is missing a themeinfo.xml file.
462010-12-19 22:48:39.223 ThemeInfo, Warning: Unable to open themeinfo.xml for /usr/share/mythtv/themes/Gray-OSD/themeinfo.xml
472010-12-19 22:48:39.223 ThemeInfo, Error: The theme (/usr/share/mythtv/themes/Gray-OSD) is missing a themeinfo.xml file.
482010-12-19 22:48:39.224 ThemeInfo, Warning: Unable to open themeinfo.xml for /usr/share/mythtv/themes/ProjectGrayhem-OSD/themeinfo.xml
492010-12-19 22:48:39.224 ThemeInfo, Error: The theme (/usr/share/mythtv/themes/ProjectGrayhem-OSD) is missing a themeinfo.xml file.
502010-12-19 22:48:39.690 Registering Internal as a media playback plugin.
512010-12-19 22:48:39.704 Loading en_us translation for module mythgame
522010-12-19 22:48:39.717 Current MythVideo Schema Version (mythvideo.DBSchemaVer): 1038
532010-12-19 22:48:39.770 MediaMonitorUnix::AddDevice() - empty device path.
542010-12-19 22:48:39.770 MediaMonitorUnix::AddDevice() - empty device path.
552010-12-19 22:48:39.770 MediaMonitorUnix::AddDevice() - empty device path.
562010-12-19 22:48:39.772 Loading en_us translation for module mythvideo
572010-12-19 22:48:40.093 Found mainmenu.xml for theme 'MythCenter-wide'
582010-12-19 22:48:40.326 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
592010-12-19 22:48:47.327 MythSocket(8dd91d0:52): readStringList: Error, timed out after 7000 ms.
602010-12-19 22:48:47.327 Protocol version check failure.
61                        The response to MYTH_PROTO_VERSION was empty.
62                        This happens when the backend is too busy to respond,
63                        or has deadlocked in due to bugs or hardware failure.
642010-12-19 22:48:47.328 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
652010-12-19 22:48:54.328 MythSocket(904f230:52): readStringList: Error, timed out after 7000 ms.
662010-12-19 22:48:54.328 Protocol version check failure.
67                        The response to MYTH_PROTO_VERSION was empty.
68                        This happens when the backend is too busy to respond,
69                        or has deadlocked in due to bugs or hardware failure.
702010-12-19 22:48:54.359 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
712010-12-19 22:49:01.359 MythSocket(98098b0:57): readStringList: Error, timed out after 7000 ms.
722010-12-19 22:49:01.359 Protocol version check failure.
73                        The response to MYTH_PROTO_VERSION was empty.
74                        This happens when the backend is too busy to respond,
75                        or has deadlocked in due to bugs or hardware failure.
762010-12-19 22:49:01.359 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
772010-12-19 22:49:01.361 PlaybackBox Error: SortedList is Empty
782010-12-19 22:49:01.474 PlaybackBox Error: SortedList is Empty
792010-12-19 22:49:08.361 MythSocket(9968d80:52): readStringList: Error, timed out after 7000 ms.
802010-12-19 22:49:08.361 Protocol version check failure.
81                        The response to MYTH_PROTO_VERSION was empty.
82                        This happens when the backend is too busy to respond,
83                        or has deadlocked in due to bugs or hardware failure.
842010-12-19 22:49:08.361 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
852010-12-19 22:49:15.362 MythSocket(984a1f8:44): readStringList: Error, timed out after 7000 ms.
862010-12-19 22:49:15.362 Protocol version check failure.
87                        The response to MYTH_PROTO_VERSION was empty.
88                        This happens when the backend is too busy to respond,
89                        or has deadlocked in due to bugs or hardware failure.
902010-12-19 22:49:15.362 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
912010-12-19 22:49:22.366 MythSocket(9968d80:44): readStringList: Error, timed out after 7000 ms.
922010-12-19 22:49:22.366 Protocol version check failure.
93                        The response to MYTH_PROTO_VERSION was empty.
94                        This happens when the backend is too busy to respond,
95                        or has deadlocked in due to bugs or hardware failure.
962010-12-19 22:49:27.366 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
972010-12-19 22:49:34.366 MythSocket(98089b8:44): readStringList: Error, timed out after 7000 ms.
982010-12-19 22:49:34.367 Protocol version check failure.
99                        The response to MYTH_PROTO_VERSION was empty.
100                        This happens when the backend is too busy to respond,
101                        or has deadlocked in due to bugs or hardware failure.
1022010-12-19 22:49:34.367 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1032010-12-19 22:49:41.371 MythSocket(999ce10:44): readStringList: Error, timed out after 7000 ms.
1042010-12-19 22:49:41.371 Protocol version check failure.
105                        The response to MYTH_PROTO_VERSION was empty.
106                        This happens when the backend is too busy to respond,
107                        or has deadlocked in due to bugs or hardware failure.
1082010-12-19 22:49:41.371 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1092010-12-19 22:49:48.374 MythSocket(9966cb8:44): readStringList: Error, timed out after 7000 ms.
1102010-12-19 22:49:48.375 Protocol version check failure.
111                        The response to MYTH_PROTO_VERSION was empty.
112                        This happens when the backend is too busy to respond,
113                        or has deadlocked in due to bugs or hardware failure.
1142010-12-19 22:49:51.122 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1152010-12-19 22:49:58.123 MythSocket(968de50:52): readStringList: Error, timed out after 7000 ms.
1162010-12-19 22:49:58.123 Protocol version check failure.
117                        The response to MYTH_PROTO_VERSION was empty.
118                        This happens when the backend is too busy to respond,
119                        or has deadlocked in due to bugs or hardware failure.
1202010-12-19 22:49:58.124 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1212010-12-19 22:49:58.124 PlaybackBox Error: SortedList is Empty
1222010-12-19 22:49:58.233 PlaybackBox Error: SortedList is Empty
1232010-12-19 22:50:05.125 MythSocket(904f230:52): readStringList: Error, timed out after 7000 ms.
1242010-12-19 22:50:05.125 Protocol version check failure.
125                        The response to MYTH_PROTO_VERSION was empty.
126                        This happens when the backend is too busy to respond,
127                        or has deadlocked in due to bugs or hardware failure.
1282010-12-19 22:50:05.125 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1292010-12-19 22:50:12.126 MythSocket(996d1c8:52): readStringList: Error, timed out after 7000 ms.
1302010-12-19 22:50:12.126 Protocol version check failure.
131                        The response to MYTH_PROTO_VERSION was empty.
132                        This happens when the backend is too busy to respond,
133                        or has deadlocked in due to bugs or hardware failure.
1342010-12-19 22:50:12.126 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1352010-12-19 22:50:19.126 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
1362010-12-19 22:50:19.126 Protocol version check failure.
137                        The response to MYTH_PROTO_VERSION was empty.
138                        This happens when the backend is too busy to respond,
139                        or has deadlocked in due to bugs or hardware failure.
1402010-12-19 22:50:24.126 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1412010-12-19 22:50:31.128 MythSocket(983b278:52): readStringList: Error, timed out after 7000 ms.
1422010-12-19 22:50:31.128 Protocol version check failure.
143                        The response to MYTH_PROTO_VERSION was empty.
144                        This happens when the backend is too busy to respond,
145                        or has deadlocked in due to bugs or hardware failure.
1462010-12-19 22:50:31.128 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1472010-12-19 22:50:38.131 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
1482010-12-19 22:50:38.131 Protocol version check failure.
149                        The response to MYTH_PROTO_VERSION was empty.
150                        This happens when the backend is too busy to respond,
151                        or has deadlocked in due to bugs or hardware failure.
1522010-12-19 22:50:38.131 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1532010-12-19 22:50:45.134 MythSocket(93f82a0:52): readStringList: Error, timed out after 7000 ms.
1542010-12-19 22:50:45.134 Protocol version check failure.
155                        The response to MYTH_PROTO_VERSION was empty.
156                        This happens when the backend is too busy to respond,
157                        or has deadlocked in due to bugs or hardware failure.
1582010-12-19 22:50:50.134 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1592010-12-19 22:50:57.136 MythSocket(97be1b0:52): readStringList: Error, timed out after 7000 ms.
1602010-12-19 22:50:57.136 Protocol version check failure.
161                        The response to MYTH_PROTO_VERSION was empty.
162                        This happens when the backend is too busy to respond,
163                        or has deadlocked in due to bugs or hardware failure.
1642010-12-19 22:50:57.136 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1652010-12-19 22:51:04.140 MythSocket(904f230:52): readStringList: Error, timed out after 7000 ms.
1662010-12-19 22:51:04.140 Protocol version check failure.
167                        The response to MYTH_PROTO_VERSION was empty.
168                        This happens when the backend is too busy to respond,
169                        or has deadlocked in due to bugs or hardware failure.
1702010-12-19 22:51:04.140 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1712010-12-19 22:51:11.140 MythSocket(996d1c8:52): readStringList: Error, timed out after 7000 ms.
1722010-12-19 22:51:11.140 Protocol version check failure.
173                        The response to MYTH_PROTO_VERSION was empty.
174                        This happens when the backend is too busy to respond,
175                        or has deadlocked in due to bugs or hardware failure.
1762010-12-19 22:51:16.140 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1772010-12-19 22:51:23.143 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
1782010-12-19 22:51:23.143 Protocol version check failure.
179                        The response to MYTH_PROTO_VERSION was empty.
180                        This happens when the backend is too busy to respond,
181                        or has deadlocked in due to bugs or hardware failure.
1822010-12-19 22:51:23.143 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1832010-12-19 22:51:30.143 MythSocket(983b278:52): readStringList: Error, timed out after 7000 ms.
1842010-12-19 22:51:30.143 Protocol version check failure.
185                        The response to MYTH_PROTO_VERSION was empty.
186                        This happens when the backend is too busy to respond,
187                        or has deadlocked in due to bugs or hardware failure.
1882010-12-19 22:51:30.143 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1892010-12-19 22:51:37.144 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
1902010-12-19 22:51:37.144 Protocol version check failure.
191                        The response to MYTH_PROTO_VERSION was empty.
192                        This happens when the backend is too busy to respond,
193                        or has deadlocked in due to bugs or hardware failure.
1942010-12-19 22:51:39.013 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
1952010-12-19 22:51:46.016 MythSocket(9b61788:52): readStringList: Error, timed out after 7000 ms.
1962010-12-19 22:51:46.016 Protocol version check failure.
197                        The response to MYTH_PROTO_VERSION was empty.
198                        This happens when the backend is too busy to respond,
199                        or has deadlocked in due to bugs or hardware failure.
2002010-12-19 22:51:46.016 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2012010-12-19 22:51:46.016 PlaybackBox Error: SortedList is Empty
2022010-12-19 22:51:46.120 PlaybackBox Error: SortedList is Empty
2032010-12-19 22:51:53.021 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
2042010-12-19 22:51:53.021 Protocol version check failure.
205                        The response to MYTH_PROTO_VERSION was empty.
206                        This happens when the backend is too busy to respond,
207                        or has deadlocked in due to bugs or hardware failure.
2082010-12-19 22:51:53.021 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2092010-12-19 22:52:00.022 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
2102010-12-19 22:52:00.023 Protocol version check failure.
211                        The response to MYTH_PROTO_VERSION was empty.
212                        This happens when the backend is too busy to respond,
213                        or has deadlocked in due to bugs or hardware failure.
2142010-12-19 22:52:00.023 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2152010-12-19 22:52:07.023 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
2162010-12-19 22:52:07.023 Protocol version check failure.
217                        The response to MYTH_PROTO_VERSION was empty.
218                        This happens when the backend is too busy to respond,
219                        or has deadlocked in due to bugs or hardware failure.
2202010-12-19 22:52:12.024 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2212010-12-19 22:52:19.027 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
2222010-12-19 22:52:19.027 Protocol version check failure.
223                        The response to MYTH_PROTO_VERSION was empty.
224                        This happens when the backend is too busy to respond,
225                        or has deadlocked in due to bugs or hardware failure.
2262010-12-19 22:52:19.027 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2272010-12-19 22:52:26.027 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
2282010-12-19 22:52:26.027 Protocol version check failure.
229                        The response to MYTH_PROTO_VERSION was empty.
230                        This happens when the backend is too busy to respond,
231                        or has deadlocked in due to bugs or hardware failure.
2322010-12-19 22:52:26.027 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2332010-12-19 22:52:33.028 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
2342010-12-19 22:52:33.029 Protocol version check failure.
235                        The response to MYTH_PROTO_VERSION was empty.
236                        This happens when the backend is too busy to respond,
237                        or has deadlocked in due to bugs or hardware failure.
2382010-12-19 22:52:38.029 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2392010-12-19 22:52:45.032 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
2402010-12-19 22:52:45.032 Protocol version check failure.
241                        The response to MYTH_PROTO_VERSION was empty.
242                        This happens when the backend is too busy to respond,
243                        or has deadlocked in due to bugs or hardware failure.
2442010-12-19 22:52:45.033 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2452010-12-19 22:52:52.036 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
2462010-12-19 22:52:52.036 Protocol version check failure.
247                        The response to MYTH_PROTO_VERSION was empty.
248                        This happens when the backend is too busy to respond,
249                        or has deadlocked in due to bugs or hardware failure.
2502010-12-19 22:52:52.036 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2512010-12-19 22:52:59.040 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
2522010-12-19 22:52:59.040 Protocol version check failure.
253                        The response to MYTH_PROTO_VERSION was empty.
254                        This happens when the backend is too busy to respond,
255                        or has deadlocked in due to bugs or hardware failure.
2562010-12-19 22:53:04.040 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2572010-12-19 22:53:11.041 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
2582010-12-19 22:53:11.041 Protocol version check failure.
259                        The response to MYTH_PROTO_VERSION was empty.
260                        This happens when the backend is too busy to respond,
261                        or has deadlocked in due to bugs or hardware failure.
2622010-12-19 22:53:11.042 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2632010-12-19 22:53:18.043 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
2642010-12-19 22:53:18.043 Protocol version check failure.
265                        The response to MYTH_PROTO_VERSION was empty.
266                        This happens when the backend is too busy to respond,
267                        or has deadlocked in due to bugs or hardware failure.
2682010-12-19 22:53:18.043 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2692010-12-19 22:53:25.046 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
2702010-12-19 22:53:25.046 Protocol version check failure.
271                        The response to MYTH_PROTO_VERSION was empty.
272                        This happens when the backend is too busy to respond,
273                        or has deadlocked in due to bugs or hardware failure.
2742010-12-19 22:53:30.046 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2752010-12-19 22:53:37.049 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
2762010-12-19 22:53:37.049 Protocol version check failure.
277                        The response to MYTH_PROTO_VERSION was empty.
278                        This happens when the backend is too busy to respond,
279                        or has deadlocked in due to bugs or hardware failure.
2802010-12-19 22:53:37.049 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2812010-12-19 22:53:44.049 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
2822010-12-19 22:53:44.050 Protocol version check failure.
283                        The response to MYTH_PROTO_VERSION was empty.
284                        This happens when the backend is too busy to respond,
285                        or has deadlocked in due to bugs or hardware failure.
2862010-12-19 22:53:44.050 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2872010-12-19 22:53:51.054 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
2882010-12-19 22:53:51.054 Protocol version check failure.
289                        The response to MYTH_PROTO_VERSION was empty.
290                        This happens when the backend is too busy to respond,
291                        or has deadlocked in due to bugs or hardware failure.
2922010-12-19 22:53:56.054 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2932010-12-19 22:54:03.058 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
2942010-12-19 22:54:03.058 Protocol version check failure.
295                        The response to MYTH_PROTO_VERSION was empty.
296                        This happens when the backend is too busy to respond,
297                        or has deadlocked in due to bugs or hardware failure.
2982010-12-19 22:54:03.058 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
2992010-12-19 22:54:10.063 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
3002010-12-19 22:54:10.063 Protocol version check failure.
301                        The response to MYTH_PROTO_VERSION was empty.
302                        This happens when the backend is too busy to respond,
303                        or has deadlocked in due to bugs or hardware failure.
3042010-12-19 22:54:10.063 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3052010-12-19 22:54:17.065 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
3062010-12-19 22:54:17.065 Protocol version check failure.
307                        The response to MYTH_PROTO_VERSION was empty.
308                        This happens when the backend is too busy to respond,
309                        or has deadlocked in due to bugs or hardware failure.
3102010-12-19 22:54:22.066 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3112010-12-19 22:54:29.068 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
3122010-12-19 22:54:29.069 Protocol version check failure.
313                        The response to MYTH_PROTO_VERSION was empty.
314                        This happens when the backend is too busy to respond,
315                        or has deadlocked in due to bugs or hardware failure.
3162010-12-19 22:54:29.069 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3172010-12-19 22:54:36.073 MythSocket(9611d38:52): readStringList: Error, timed out after 7000 ms.
3182010-12-19 22:54:36.073 Protocol version check failure.
319                        The response to MYTH_PROTO_VERSION was empty.
320                        This happens when the backend is too busy to respond,
321                        or has deadlocked in due to bugs or hardware failure.
3222010-12-19 22:54:36.074 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3232010-12-19 22:54:43.075 MythSocket(999c6f0:52): readStringList: Error, timed out after 7000 ms.
3242010-12-19 22:54:43.075 Protocol version check failure.
325                        The response to MYTH_PROTO_VERSION was empty.
326                        This happens when the backend is too busy to respond,
327                        or has deadlocked in due to bugs or hardware failure.
3282010-12-19 22:54:48.075 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3292010-12-19 22:54:55.076 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
3302010-12-19 22:54:55.076 Protocol version check failure.
331                        The response to MYTH_PROTO_VERSION was empty.
332                        This happens when the backend is too busy to respond,
333                        or has deadlocked in due to bugs or hardware failure.
3342010-12-19 22:54:55.077 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3352010-12-19 22:55:02.080 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
3362010-12-19 22:55:02.081 Protocol version check failure.
337                        The response to MYTH_PROTO_VERSION was empty.
338                        This happens when the backend is too busy to respond,
339                        or has deadlocked in due to bugs or hardware failure.
3402010-12-19 22:55:02.081 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3412010-12-19 22:55:09.084 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
3422010-12-19 22:55:09.084 Protocol version check failure.
343                        The response to MYTH_PROTO_VERSION was empty.
344                        This happens when the backend is too busy to respond,
345                        or has deadlocked in due to bugs or hardware failure.
3462010-12-19 22:55:14.085 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3472010-12-19 22:55:21.088 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
3482010-12-19 22:55:21.088 Protocol version check failure.
349                        The response to MYTH_PROTO_VERSION was empty.
350                        This happens when the backend is too busy to respond,
351                        or has deadlocked in due to bugs or hardware failure.
3522010-12-19 22:55:21.088 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3532010-12-19 22:55:28.093 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
3542010-12-19 22:55:28.094 Protocol version check failure.
355                        The response to MYTH_PROTO_VERSION was empty.
356                        This happens when the backend is too busy to respond,
357                        or has deadlocked in due to bugs or hardware failure.
3582010-12-19 22:55:28.094 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3592010-12-19 22:55:35.094 MythSocket(9611d38:52): readStringList: Error, timed out after 7000 ms.
3602010-12-19 22:55:35.095 Protocol version check failure.
361                        The response to MYTH_PROTO_VERSION was empty.
362                        This happens when the backend is too busy to respond,
363                        or has deadlocked in due to bugs or hardware failure.
3642010-12-19 22:55:40.095 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3652010-12-19 22:55:47.095 MythSocket(999c6f0:52): readStringList: Error, timed out after 7000 ms.
3662010-12-19 22:55:47.095 Protocol version check failure.
367                        The response to MYTH_PROTO_VERSION was empty.
368                        This happens when the backend is too busy to respond,
369                        or has deadlocked in due to bugs or hardware failure.
3702010-12-19 22:55:47.095 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3712010-12-19 22:55:54.097 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
3722010-12-19 22:55:54.098 Protocol version check failure.
373                        The response to MYTH_PROTO_VERSION was empty.
374                        This happens when the backend is too busy to respond,
375                        or has deadlocked in due to bugs or hardware failure.
3762010-12-19 22:55:54.098 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3772010-12-19 22:56:01.100 MythSocket(999c6f0:52): readStringList: Error, timed out after 7000 ms.
3782010-12-19 22:56:01.100 Protocol version check failure.
379                        The response to MYTH_PROTO_VERSION was empty.
380                        This happens when the backend is too busy to respond,
381                        or has deadlocked in due to bugs or hardware failure.
3822010-12-19 22:56:06.100 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3832010-12-19 22:56:13.105 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
3842010-12-19 22:56:13.105 Protocol version check failure.
385                        The response to MYTH_PROTO_VERSION was empty.
386                        This happens when the backend is too busy to respond,
387                        or has deadlocked in due to bugs or hardware failure.
3882010-12-19 22:56:13.105 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3892010-12-19 22:56:20.110 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
3902010-12-19 22:56:20.110 Protocol version check failure.
391                        The response to MYTH_PROTO_VERSION was empty.
392                        This happens when the backend is too busy to respond,
393                        or has deadlocked in due to bugs or hardware failure.
3942010-12-19 22:56:20.110 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
3952010-12-19 22:56:27.114 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
3962010-12-19 22:56:27.114 Protocol version check failure.
397                        The response to MYTH_PROTO_VERSION was empty.
398                        This happens when the backend is too busy to respond,
399                        or has deadlocked in due to bugs or hardware failure.
4002010-12-19 22:56:32.115 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4012010-12-19 22:56:39.115 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
4022010-12-19 22:56:39.115 Protocol version check failure.
403                        The response to MYTH_PROTO_VERSION was empty.
404                        This happens when the backend is too busy to respond,
405                        or has deadlocked in due to bugs or hardware failure.
4062010-12-19 22:56:39.115 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4072010-12-19 22:56:46.118 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
4082010-12-19 22:56:46.118 Protocol version check failure.
409                        The response to MYTH_PROTO_VERSION was empty.
410                        This happens when the backend is too busy to respond,
411                        or has deadlocked in due to bugs or hardware failure.
4122010-12-19 22:56:46.118 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4132010-12-19 22:56:53.122 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
4142010-12-19 22:56:53.122 Protocol version check failure.
415                        The response to MYTH_PROTO_VERSION was empty.
416                        This happens when the backend is too busy to respond,
417                        or has deadlocked in due to bugs or hardware failure.
4182010-12-19 22:56:58.122 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4192010-12-19 22:57:05.124 MythSocket(999c6f0:52): readStringList: Error, timed out after 7000 ms.
4202010-12-19 22:57:05.124 Protocol version check failure.
421                        The response to MYTH_PROTO_VERSION was empty.
422                        This happens when the backend is too busy to respond,
423                        or has deadlocked in due to bugs or hardware failure.
4242010-12-19 22:57:05.124 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4252010-12-19 22:57:12.125 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
4262010-12-19 22:57:12.125 Protocol version check failure.
427                        The response to MYTH_PROTO_VERSION was empty.
428                        This happens when the backend is too busy to respond,
429                        or has deadlocked in due to bugs or hardware failure.
4302010-12-19 22:57:12.125 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4312010-12-19 22:57:19.130 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
4322010-12-19 22:57:19.130 Protocol version check failure.
433                        The response to MYTH_PROTO_VERSION was empty.
434                        This happens when the backend is too busy to respond,
435                        or has deadlocked in due to bugs or hardware failure.
4362010-12-19 22:57:24.131 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4372010-12-19 22:57:31.132 MythSocket(99740d8:52): readStringList: Error, timed out after 7000 ms.
4382010-12-19 22:57:31.132 Protocol version check failure.
439                        The response to MYTH_PROTO_VERSION was empty.
440                        This happens when the backend is too busy to respond,
441                        or has deadlocked in due to bugs or hardware failure.
4422010-12-19 22:57:31.133 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4432010-12-19 22:57:38.136 MythSocket(9611d38:52): readStringList: Error, timed out after 7000 ms.
4442010-12-19 22:57:38.137 Protocol version check failure.
445                        The response to MYTH_PROTO_VERSION was empty.
446                        This happens when the backend is too busy to respond,
447                        or has deadlocked in due to bugs or hardware failure.
4482010-12-19 22:57:38.137 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4492010-12-19 22:57:45.140 MythSocket(9824408:52): readStringList: Error, timed out after 7000 ms.
4502010-12-19 22:57:45.140 Protocol version check failure.
451                        The response to MYTH_PROTO_VERSION was empty.
452                        This happens when the backend is too busy to respond,
453                        or has deadlocked in due to bugs or hardware failure.
4542010-12-19 22:57:50.140 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4552010-12-19 22:57:57.142 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
4562010-12-19 22:57:57.142 Protocol version check failure.
457                        The response to MYTH_PROTO_VERSION was empty.
458                        This happens when the backend is too busy to respond,
459                        or has deadlocked in due to bugs or hardware failure.
4602010-12-19 22:57:57.142 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4612010-12-19 22:58:04.146 MythSocket(9850bd8:52): readStringList: Error, timed out after 7000 ms.
4622010-12-19 22:58:04.146 Protocol version check failure.
463                        The response to MYTH_PROTO_VERSION was empty.
464                        This happens when the backend is too busy to respond,
465                        or has deadlocked in due to bugs or hardware failure.
4662010-12-19 22:58:04.146 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4672010-12-19 22:58:11.146 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
4682010-12-19 22:58:11.146 Protocol version check failure.
469                        The response to MYTH_PROTO_VERSION was empty.
470                        This happens when the backend is too busy to respond,
471                        or has deadlocked in due to bugs or hardware failure.
4722010-12-19 22:58:16.146 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4732010-12-19 22:58:23.151 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
4742010-12-19 22:58:23.151 Protocol version check failure.
475                        The response to MYTH_PROTO_VERSION was empty.
476                        This happens when the backend is too busy to respond,
477                        or has deadlocked in due to bugs or hardware failure.
4782010-12-19 22:58:23.151 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4792010-12-19 22:58:30.154 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
4802010-12-19 22:58:30.154 Protocol version check failure.
481                        The response to MYTH_PROTO_VERSION was empty.
482                        This happens when the backend is too busy to respond,
483                        or has deadlocked in due to bugs or hardware failure.
4842010-12-19 22:58:30.154 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4852010-12-19 22:58:37.156 MythSocket(9850bd8:52): readStringList: Error, timed out after 7000 ms.
4862010-12-19 22:58:37.156 Protocol version check failure.
487                        The response to MYTH_PROTO_VERSION was empty.
488                        This happens when the backend is too busy to respond,
489                        or has deadlocked in due to bugs or hardware failure.
4902010-12-19 22:58:42.157 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4912010-12-19 22:58:49.162 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
4922010-12-19 22:58:49.162 Protocol version check failure.
493                        The response to MYTH_PROTO_VERSION was empty.
494                        This happens when the backend is too busy to respond,
495                        or has deadlocked in due to bugs or hardware failure.
4962010-12-19 22:58:49.162 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
4972010-12-19 22:58:56.166 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
4982010-12-19 22:58:56.166 Protocol version check failure.
499                        The response to MYTH_PROTO_VERSION was empty.
500                        This happens when the backend is too busy to respond,
501                        or has deadlocked in due to bugs or hardware failure.
5022010-12-19 22:58:56.166 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5032010-12-19 22:59:03.168 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
5042010-12-19 22:59:03.169 Protocol version check failure.
505                        The response to MYTH_PROTO_VERSION was empty.
506                        This happens when the backend is too busy to respond,
507                        or has deadlocked in due to bugs or hardware failure.
5082010-12-19 22:59:08.169 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5092010-12-19 22:59:15.172 MythSocket(9850bd8:52): readStringList: Error, timed out after 7000 ms.
5102010-12-19 22:59:15.172 Protocol version check failure.
511                        The response to MYTH_PROTO_VERSION was empty.
512                        This happens when the backend is too busy to respond,
513                        or has deadlocked in due to bugs or hardware failure.
5142010-12-19 22:59:15.172 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5152010-12-19 22:59:22.177 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
5162010-12-19 22:59:22.177 Protocol version check failure.
517                        The response to MYTH_PROTO_VERSION was empty.
518                        This happens when the backend is too busy to respond,
519                        or has deadlocked in due to bugs or hardware failure.
5202010-12-19 22:59:22.177 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5212010-12-19 22:59:29.181 MythSocket(9b9e520:52): readStringList: Error, timed out after 7000 ms.
5222010-12-19 22:59:29.181 Protocol version check failure.
523                        The response to MYTH_PROTO_VERSION was empty.
524                        This happens when the backend is too busy to respond,
525                        or has deadlocked in due to bugs or hardware failure.
5262010-12-19 22:59:34.182 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5272010-12-19 22:59:41.186 MythSocket(999d180:52): readStringList: Error, timed out after 7000 ms.
5282010-12-19 22:59:41.186 Protocol version check failure.
529                        The response to MYTH_PROTO_VERSION was empty.
530                        This happens when the backend is too busy to respond,
531                        or has deadlocked in due to bugs or hardware failure.
5322010-12-19 22:59:41.186 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5332010-12-19 22:59:48.187 MythSocket(9850bd8:52): readStringList: Error, timed out after 7000 ms.
5342010-12-19 22:59:48.187 Protocol version check failure.
535                        The response to MYTH_PROTO_VERSION was empty.
536                        This happens when the backend is too busy to respond,
537                        or has deadlocked in due to bugs or hardware failure.
5382010-12-19 22:59:48.187 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5392010-12-19 22:59:55.190 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
5402010-12-19 22:59:55.190 Protocol version check failure.
541                        The response to MYTH_PROTO_VERSION was empty.
542                        This happens when the backend is too busy to respond,
543                        or has deadlocked in due to bugs or hardware failure.
5442010-12-19 23:00:00.190 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5452010-12-19 23:00:07.194 MythSocket(98aa050:52): readStringList: Error, timed out after 7000 ms.
5462010-12-19 23:00:07.194 Protocol version check failure.
547                        The response to MYTH_PROTO_VERSION was empty.
548                        This happens when the backend is too busy to respond,
549                        or has deadlocked in due to bugs or hardware failure.
5502010-12-19 23:00:07.194 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5512010-12-19 23:00:14.197 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
5522010-12-19 23:00:14.197 Protocol version check failure.
553                        The response to MYTH_PROTO_VERSION was empty.
554                        This happens when the backend is too busy to respond,
555                        or has deadlocked in due to bugs or hardware failure.
5562010-12-19 23:00:14.197 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5572010-12-19 23:00:21.198 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
5582010-12-19 23:00:21.198 Protocol version check failure.
559                        The response to MYTH_PROTO_VERSION was empty.
560                        This happens when the backend is too busy to respond,
561                        or has deadlocked in due to bugs or hardware failure.
5622010-12-19 23:00:26.199 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5632010-12-19 23:00:33.203 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
5642010-12-19 23:00:33.203 Protocol version check failure.
565                        The response to MYTH_PROTO_VERSION was empty.
566                        This happens when the backend is too busy to respond,
567                        or has deadlocked in due to bugs or hardware failure.
5682010-12-19 23:00:33.204 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5692010-12-19 23:00:40.206 MythSocket(98aa050:52): readStringList: Error, timed out after 7000 ms.
5702010-12-19 23:00:40.206 Protocol version check failure.
571                        The response to MYTH_PROTO_VERSION was empty.
572                        This happens when the backend is too busy to respond,
573                        or has deadlocked in due to bugs or hardware failure.
5742010-12-19 23:00:40.207 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5752010-12-19 23:00:47.208 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
5762010-12-19 23:00:47.208 Protocol version check failure.
577                        The response to MYTH_PROTO_VERSION was empty.
578                        This happens when the backend is too busy to respond,
579                        or has deadlocked in due to bugs or hardware failure.
5802010-12-19 23:00:52.209 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5812010-12-19 23:00:59.211 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
5822010-12-19 23:00:59.211 Protocol version check failure.
583                        The response to MYTH_PROTO_VERSION was empty.
584                        This happens when the backend is too busy to respond,
585                        or has deadlocked in due to bugs or hardware failure.
5862010-12-19 23:00:59.212 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5872010-12-19 23:01:06.213 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
5882010-12-19 23:01:06.213 Protocol version check failure.
589                        The response to MYTH_PROTO_VERSION was empty.
590                        This happens when the backend is too busy to respond,
591                        or has deadlocked in due to bugs or hardware failure.
5922010-12-19 23:01:06.214 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5932010-12-19 23:01:13.217 MythSocket(98aa050:52): readStringList: Error, timed out after 7000 ms.
5942010-12-19 23:01:13.217 Protocol version check failure.
595                        The response to MYTH_PROTO_VERSION was empty.
596                        This happens when the backend is too busy to respond,
597                        or has deadlocked in due to bugs or hardware failure.
5982010-12-19 23:01:18.217 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
5992010-12-19 23:01:25.219 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
6002010-12-19 23:01:25.219 Protocol version check failure.
601                        The response to MYTH_PROTO_VERSION was empty.
602                        This happens when the backend is too busy to respond,
603                        or has deadlocked in due to bugs or hardware failure.
6042010-12-19 23:01:25.220 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6052010-12-19 23:01:32.225 MythSocket(9964968:52): readStringList: Error, timed out after 7000 ms.
6062010-12-19 23:01:32.225 Protocol version check failure.
607                        The response to MYTH_PROTO_VERSION was empty.
608                        This happens when the backend is too busy to respond,
609                        or has deadlocked in due to bugs or hardware failure.
6102010-12-19 23:01:32.225 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6112010-12-19 23:01:39.227 MythSocket(9997170:52): readStringList: Error, timed out after 7000 ms.
6122010-12-19 23:01:39.227 Protocol version check failure.
613                        The response to MYTH_PROTO_VERSION was empty.
614                        This happens when the backend is too busy to respond,
615                        or has deadlocked in due to bugs or hardware failure.
6162010-12-19 23:01:44.227 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6172010-12-19 23:01:51.228 MythSocket(98aa050:52): readStringList: Error, timed out after 7000 ms.
6182010-12-19 23:01:51.228 Protocol version check failure.
619                        The response to MYTH_PROTO_VERSION was empty.
620                        This happens when the backend is too busy to respond,
621                        or has deadlocked in due to bugs or hardware failure.
6222010-12-19 23:01:51.228 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6232010-12-19 23:01:58.231 MythSocket(97f7ad0:52): readStringList: Error, timed out after 7000 ms.
6242010-12-19 23:01:58.231 Protocol version check failure.
625                        The response to MYTH_PROTO_VERSION was empty.
626                        This happens when the backend is too busy to respond,
627                        or has deadlocked in due to bugs or hardware failure.
6282010-12-19 23:01:58.231 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6292010-12-19 23:02:05.233 MythSocket(999c6f0:52): readStringList: Error, timed out after 7000 ms.
6302010-12-19 23:02:05.233 Protocol version check failure.
631                        The response to MYTH_PROTO_VERSION was empty.
632                        This happens when the backend is too busy to respond,
633                        or has deadlocked in due to bugs or hardware failure.
6342010-12-19 23:02:10.234 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6352010-12-19 23:02:17.238 MythSocket(9611d38:52): readStringList: Error, timed out after 7000 ms.
6362010-12-19 23:02:17.238 Protocol version check failure.
637                        The response to MYTH_PROTO_VERSION was empty.
638                        This happens when the backend is too busy to respond,
639                        or has deadlocked in due to bugs or hardware failure.
6402010-12-19 23:02:17.238 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)
6412010-12-19 23:02:24.240 MythSocket(965c4c8:52): readStringList: Error, timed out after 7000 ms.
6422010-12-19 23:02:24.240 Protocol version check failure.
643                        The response to MYTH_PROTO_VERSION was empty.
644                        This happens when the backend is too busy to respond,
645                        or has deadlocked in due to bugs or hardware failure.
6462010-12-19 23:02:24.240 MythCoreContext: Connecting to backend server: 10.75.22.2:6543 (try 1 of 5)