[mythtv-users] Overactive scheduler?

[Marco Quezada]

>On 02/10/2012 05:11 PM, Marco Quezada wrote:
>> My backend has trouble reaching an idle timeout so it can shutdown on
>> its own. Its logs are filled with entries like these:
>>
>>
>> 2012-02-10 16:38:57.396 mythbackend: Running housekeeping thread
>> 2012-02-10 16:39:28.000 MainServer::ANN Playback
>> 2012-02-10 16:39:28.002 adding: QMHTPC-1 as a client (events: 0)
>> 2012-02-10 16:39:28.005 MainServer::ANN Monitor
>> 2012-02-10 16:39:28.016 adding: QMHTPC-1 as a client (events: 1)
>> 2012-02-10 16:39:28.019 Reschedule requested for id -1.
>> 2012-02-10 16:39:29.434 Scheduled 144 items in 1.4 = 0.02 match + 1.37 place
>> 2012-02-10 16:39:29.441 scheduler: Scheduled items: Scheduled 144
>> items in 1.4 = 0.02 match + 1.37 place
>> 2012-02-10 16:40:07.397 AutoExpire: CalcParams(): Max required Free
>> Space: 1.0 GB w/freq: 15 min
>> 2012-02-10 16:42:51.110 MainServer::ANN Monitor
>> 2012-02-10 16:42:51.111 adding: QMHTPC-1 as a client (events: 2)
>> 2012-02-10 16:42:51.600 MainServer::ANN Monitor
>> 2012-02-10 16:42:51.606 adding: QMHTPC-1 as a client (events: 2)
>> 2012-02-10 16:45:02.602 MainServer::ANN Monitor
>> 2012-02-10 16:45:02.606 adding: QMHTPC-1 as a client (events: 2)
>> 2012-02-10 16:55:07.627 AutoExpire: CalcParams(): Max required Free
>> Space: 1.0 GB w/freq: 15 min
>>
>> So I suspect that the scheduler is keeping it awake but I am not sure
>> which settings I may have messed up. The information I have found
>> online seems to indicate an issue with the EIT grabber but I am not
>> using EIT, I am using Schedules Direct. I am using mythTV version
>> "fixes/0.24 [v0.24-243-g9ba3ece]".
>>
>> I've reduced the idle timeout to 600 secs and the idle wait for
>> recording time to 20 minutes but cannot seem to be able to get ahead
>> of the scheduler or the housekeeping thread. The permissions for
>> executing the shutdown script and setting the time on the RTC are
>> correct, every once in a loooong while the machine seems to reach the
>> idle timeout and it does shutdown, but it takes weeks some times.
>>
>> I've tried looking for information on the AutoExpire, Scheduled items
>> and housekeeping messages to try to track them down but have not had
>> much luck. Am I even on the correct track or might there be another
>> issue?

>You've explicitly disabled EIT on the Video Source using Schedules
>Direct data (in mythtv-setup)?
>
>Mike

Yes, I have only one Video Source configured (Schedules Direct) with
the "Perform EIT Scan" box unchecked, and I have both of my input
connections (2 tuners on my HDHR) tied to this Video Source.


I did find this snippet in my backend log from earlier in the month
when it was still set to look for an idle time of 840 seconds. It
seems it really thought it would shut down but got interrupted:

2012-02-04 17:36:39.516 Seem to be woken up by USER
2012-02-04 17:36:44.610 mythbackend: Running housekeeping thread
2012-02-04 17:36:51.324 MainServer::ANN Playback
2012-02-04 17:36:51.333 adding: QMHTPC-1 as a client (events: 0)
2012-02-04 17:36:51.336 MainServer::ANN Monitor
2012-02-04 17:36:51.353 adding: QMHTPC-1 as a client (events: 1)
2012-02-04 17:36:59.528 I'm idle now... shutdown will occur in 840 seconds.
2012-02-04 17:37:54.610 AutoExpire: CalcParams(): Max required Free
Space: 1.0 GB w/freq: 15 min
2012-02-04 17:38:50.360 MainServer::ANN Playback
2012-02-04 17:38:50.361 adding: QMHTPC-1 as a client (events: 0)
2012-02-04 17:38:50.364 MainServer::ANN Monitor
2012-02-04 17:38:50.365 adding: QMHTPC-1 as a client (events: 1)
2012-02-04 17:40:37.968 MainServer::ANN Playback
2012-02-04 17:40:37.970 adding: QMHTPC-1 as a client (events: 0)
2012-02-04 17:40:37.972 MainServer::ANN Playback
2012-02-04 17:40:37.973 adding: QMHTPC-1 as a client (events: 0)
2012-02-04 17:40:37.974 MainServer::ANN Monitor
2012-02-04 17:40:37.976 MainServer::ANN Monitor



-Marco