LinHES Forums
http://forum.linhes.org/

Yet another Mythwelcome problem
http://forum.linhes.org/viewtopic.php?f=6&t=19139		 Page 1 of 1
Author:  nmcaullay [ Thu Oct 23, 2008 7:41 pm ]
Post subject:  Yet another Mythwelcome problem
Hi All,

I've been running mythwelcome on KM for a few versions now, and generally its been a solid performer. I'm using ACPI according to the KM wiki
http://www.knoppmythwiki.org/index.php?page=MythWelcome and the myth wiki
http://www.mythtv.org/wiki/index.php/ACPI_Wakeup.

In recent weeks ive noticed that a few programs have not recorded, as the machine has not woken up. I'm not sure now if the wakeup has worked since i went to R5.5.

I run the following commends to see if my configuration is correct
Code:
mythwelcome-test-wakeup.sh
and then issue
Code:
sudo /sbin/shutdown -h now


This sets the alarm time to +4 mins, and shuts the machine down. In 4 minutes the machine wakes up. No problem. The /tmp/alarm.log looks like this

Code:
Shutdown: Thu Oct 23 14:57:32 UTC 2008
Alarm Set: 1224774003
/proc/driver/rtc:
rtc_time        : 14:57:32
rtc_date        : 2008-10-23
alrm_time       : 15:00:03
alrm_date       : ****-10-23
alarm_IRQ       : yes
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay
enabled
2079984499
Startup: Thu Oct 23 15:00:34 UTC 2008


If i schedule a program to record in 30 mins time, then mythwelcome will shutdown the computer, but it doesnt wakeup. When i manually start the machine up, the following is in /tmp/alarm.log

Code:
Shutdown: Thu Oct 23 22:37:13 UTC 2008
Alarm Set: 1224847740
/proc/driver/rtc:
rtc_time        : 22:37:13
rtc_date        : 2008-10-23
alrm_time       : 11:29:00
alrm_date       : ****-10-24
alarm_IRQ       : yes
alrm_pending    : no
24hr            : yes
periodic_IRQ    : no
update_IRQ      : no
DST_enable      : no
periodic_freq   : 1024
batt_status     : okay
enabled
2080058236
Startup: Thu Oct 23 22:53:28 UTC 2008


Now, looking at the alarm.log files above, the main difference i can see in what is logged at shutdown time is the "time-since-epoch" value. In the manual test, the correct value was set in /tmp/alarm
Code:
1224774003 = October 23rd, 2008 03:00:03 PM

In the mythwelcome shutdown, the /tmp/alarm value is ALWAYS the following
Code:
1224847740 = October 24th, 2008 11:29:00 AM


It doesnt matter when (or how many times) i let mythwelcome shutdown the machine the "time-since-epoch" value is always
Code:
1224847740 = October 24th, 2008 11:29:00 AM


So, i'm thinking that it MUST be an error in how im passing the shutdown $time value from mythbackend/mythwelcome to the mythwelcome-set-alarm.sh script? My settings for both the backend and the mythwelcome are as per the wiki detail (i believe, although it was late).

I must admit that i'm not 100% clear on which settings do what on mythbackend/mythwelcome, there seems to be some duplication of settings?

Any ideas?

Cheers,

Nathan
Author:  alien [ Fri Oct 24, 2008 2:19 am ]
Post subject: 
Did you have a show scheduled to record around October 24th, 2008 11:29:00 AM?

I noticed my box skipped a couple shows. Thinking back, I shutdown the box shortly before in both cases. This might be a bug that shows in the near future are ignored....

Try scheduling a show farther in the future. Two numbers that might prove interesting are:

1. >1 hour in the future (say 1:15)

2. Your timezone difference from UTC + 15mins (ex. if you are UTC+5, try recording something 5:15 in the future).

If that is the problem, you can increase the "Max wait for recording" parameter as a work-around.
Allen
Author:  nmcaullay [ Fri Oct 24, 2008 8:50 am ]
Post subject: 
Thanks for the reply, it seems that i might have been a bit too clever for myself.

I must have changed the setting in mythsetup from
Code:
Command to set Wakeup Time: /usr/bin/mythshutdown --setwakeup $time

to
Code:
Command to set Wakeup Time: /usr/bin/mythshutdown --settime $time


The problem being the --settime instead of --setwakeup... :)

Seems that because of this innapropriate change the "time to wakeup" was never getting passed to the KM set-alarm script, and taking a default/old value (i guess).

I have corrected it (to what the KM wiki says), and set a program to record in 10 minutes time, and it started up... excellent...

Other things is changed, possibly unrelated tonight are
1) Added /tmp/alarm and /tmp/alarm.log to /etc/sudoers

I'll probably remove this from sudoers... thanks for your help.
Hopefully this works all the time now... otherwise, i'm back to pulling hair.

Cheers,

Nathan
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/