[mythtv-users] Update to Mint 17.2 broke wakeup function.

[Hika van den Hoven]

Hoi Douglas,

Sunday, August 9, 2015, 4:18:54 AM, you wrote:

> On 08/08/2015 06:53 PM, Hika van den Hoven wrote:
>> Hoi Douglas,
>>
>> Sunday, August 9, 2015, 3:29:06 AM, you wrote:
>>
>>> On 08/08/2015 06:14 PM, Douglas Peale wrote:
>>>> On 08/08/2015 04:46 PM, Bill Meek wrote:
>>>>> On 08/08/2015 06:25 PM, Douglas Peale wrote:
>>>>>> No, This is all that is there:
>>>>>> -rw-r--r-- 1 syslog adm  7315371 Aug  8 16:24 mythbackend.log
>>>>> ...
>>>>>
>>>>> Also see if the user running the program has write permission there:
>>>>>
>>>>>     ls -ld /var/log/mythtv
>>>>>
>>>>> You might find the directory is now owned by: syslog:adm too.
>>>>>
>>>>> mythbackend --setverbose system,idle will add more logging.
>>>>> Then check /var/log/mythtv/mythbackend.log.
>>>>>
>>>> It occurs to me that there is nothing in the recording que, nothing I have scheduled to record appears in the schedule for the
>>>> two weeks of schedule that schedules direct provides.
>>>> Does mythTV still run the setwakeup.sh script if it knows of nothing to record?
>>>> This would seem like a bug to me, it should at least wakeup and download a new schedule to see if anything it needs to record
>>>> showed up.
>>>>
>>>> If this is indeed the problem, should I set a wakeup time in the checklogin.sh script (one that would get overwritten by the
>>>> setwakeup.sh script if it is run?
>>>>
>>>> I'm going to schedule something that will record in the next few days, and see if that makes a difference.
>>>>
>>>>
>>> I can confirm that this was the problem.
>>> Once something showed up in the upcoming schedule, MythTV began
>>> calling the setwakup.sh script, and log items from setwakup.sh
>>> showed up in my log file.
>>> This is a bug. Even if MythTV finds nothing to record, it should
>>> set a wakeup time before its schedule runs out so in can update
>>> its schedule.
>>> As it now stands, if mythTV ever shuts down without having anything
>>> in its schedule to record, it will never wake up on its own,
>>> and could miss future recordings.
>> If you know when the normal data fetch is scheduled, you probably
>> could add something in the script. Like if Mythtv doesn't suggest a
>> wakeup time set it to 5 minutes before the next planned datagrab.
>>
>>
>> Tot mails,
>>   Hika                            mailto:hikavdh at gmail.com
>>
>>
> This would have to be done in the checklogin.sh script since when
> mythTV does not have anything to record, it does not call the
> setwakeup.sh script.
> I have added a 3:00 AM wakup to the checklogin.sh script. I'll find out tomorrow if it works.

As said I do not know the script, my backend is on 24/7.
But if the wakeup time is not close enough to the datagrab time, you
run the chance that it closes down before it can fetch the new
schedule! So somehow you have to make sure it stays awake that long. A
possible work-around would be to schedule a daily 1 minute timed
recording around the time the data is supposed to be fetched. Set it
to only keep one copy so your database doesn't get cluttered.



Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens