I am on mythtv 0.25.2 on EL6. Lately, I've noticed that my frontend has started to hang periodically and become unresponsive to either keyboard or IR commands. Today, I dug a bit deeper and found this in my frontend log:<div>
<br></div><div><many deleted lines></div><div><div><div>2012-09-23 17:54:12.867672 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-Alerts</div><div>2012-09-23 18:04:12.882817 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-Alerts</div>
<div>2012-09-23 18:09:11.037350 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-XML</div><div>2012-09-23 18:09:11.053412 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NDFD-6_day</div>
<div>2012-09-23 18:14:12.905605 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-Alerts</div><div>2012-09-23 18:24:11.052140 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-XML</div>
<div>2012-09-23 18:24:11.075766 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NDFD-6_day</div><div>2012-09-23 18:24:12.926657 I [19851/19851] CoreContext weatherSource.cpp:424 (startUpdate) - Starting update of NWS-Alerts</div>
<div>2012-09-24 04:55:50.953133 I [19851/20084] Socket mythcorecontext.cpp:1103 (readyRead) - Received remote 'Clear Cache' request</div><div>2012-09-24 04:55:51.105931 I [19851/19981] DBLogger mythdbcon.cpp:237 (Reconnect) - MySQL reconnected successfully</div>
</div></div><div><div><big gap here></div><div>2012-09-24 19:17:51.207815 C [21248/21248] thread_unknown mythcommandlineparser.cpp:2534 (ConfigureLogging) - mythfrontend version: [v0.25.2] <a href="http://www.mythtv.org">www.mythtv.org</a></div>
<div>2012-09-24 19:17:51.207865 C [21248/21248] thread_unknown mythcommandlineparser.cpp:2536 (ConfigureLogging) - Qt version: compile: 4.7.2, runtime: 4.7.2</div><div>2012-09-24 19:17:51.207870 N [21248/21248] thread_unknown mythcommandlineparser.cpp:2538 (ConfigureLogging) - Enabled verbose msgs: general</div>
<div>2012-09-24 19:17:51.208048 N [21248/21248] thread_unknown logging.cpp:1176 (logStart) - Setting Log Level to LOG_INFO</div><div>2012-09-24 19:17:51.208132 I [21248/21248] thread_unknown logging.cpp:229 (FileLogger) - Added logging to the console</div>
<div>2012-09-24 19:17:51.208378 I [21248/21248] thread_unknown logging.cpp:238 (FileLogger) - Added logging to /var/log/mythtv/mythfrontend.20120924191751.21248.log</div><div>2012-09-24 19:17:51.208392 I [21248/21248] thread_unknown logging.cpp:425 (DatabaseLogger) - Added database logging to table logging</div>
<div>2012-09-24 19:17:51.208540 N [21248/21248] thread_unknown logging.cpp:1215 (logStart) - Setting up SIGHUP handler</div></div><div><more lines here></div><div><br></div><div>Notice the big gap in the time stamps of the frontend log. Only when I restarted at 19:17 did the frontend become responsive again. I think it was hung all day today, from 04:55 all the way up to 19:17 when I restarted.</div>
<div><br></div><div>Since the problem happened in the wee hours of the morning, it occurred to me to check the mythfilldatabase log. It has this:</div><div><br></div><div><many deleted lines></div><div><div>2012-09-24 04:52:52.557164 I Adjusting program database end times.</div>
<div>2012-09-24 04:52:58.021447 I 1 replacements made</div><div>2012-09-24 04:52:58.021464 I Marking generic episodes.</div><div>2012-09-24 04:52:59.906780 I Found 2837</div><div>2012-09-24 04:52:59.906942 I Extending non-unique programids with multiple parts.</div>
<div>2012-09-24 04:53:00.281210 I Found 0</div><div>2012-09-24 04:53:00.281281 I Marking repeats.</div><div>2012-09-24 04:53:02.756555 I Found 9052</div><div>2012-09-24 04:53:02.756577 I Unmarking new episode rebroadcast repeats.</div>
<div>2012-09-24 04:53:03.236025 I Found 0</div><div>2012-09-24 04:53:07.532096 I Marking episode first showings.</div><div>2012-09-24 04:54:30.198931 I Found 29935</div><div>2012-09-24 04:54:30.198950 I Marking episode last showings.</div>
<div>2012-09-24 04:55:48.983045 I Found 29935</div><div>2012-09-24 04:55:49.371278 I DataDirect: Grabbing next suggested grabbing time</div><div>2012-09-24 04:55:50.851191 I Suggested Time data: 612 bytes</div><div>
2012-09-24 04:55:50.857193 I DataDirect: BlockedTime is: 2012-09-24T04:55:50</div><div>2012-09-24 04:55:50.857726 I DataDirect: NextSuggestedTime is: 2012-09-25T12:27:40</div><div>2012-09-24 04:55:50.861291 I</div><div>
===============================================================</div><div>| Attempting to contact the master backend for rescheduling. |</div><div>| If the master is not running, rescheduling will happen when |</div><div>
| the master backend is restarted. |</div><div>===============================================================</div><div>2012-09-24 04:55:50.873260 I MythCoreContext: Connecting to backend server: <a href="http://192.168.1.200:6543" target="_blank">192.168.1.200:6543</a> (try 1 of 1)</div>
<div>2012-09-24 04:55:50.909066 I Using protocol version 72</div><div>2012-09-24 04:55:50.923943 N mythfilldatabase run complete.</div><div>Application asked to unregister timer 0x30000001 which is not registered in this thread. Fix application.</div>
<div>2012-09-24 04:55:51.035081 I DataDirect: Deleting temporary files</div></div><div><br></div><div><br></div><div>At 04:55 the mythfilldatabase task seems to have encountered an error that coincides with the time my frontend probably went unresponsive. The second from last error message looks like it might be a clue: Application asked to unregister timer 0x30000001 which is not registered in this thread. Fix application.</div>
<div><br></div><div>Any thoughts on what could be the problem?
</div><div><br></div><div>Larry</div>