Mailing List Archive: MythTV: Users

MythTV 0.22 Upgrade mythwelcome problem

Index | Next | Previous | View Threaded

jbut at swin

Apr 8, 2010, 4:37 PM

Post #1 of 9 (888 views)
Permalink

MythTV 0.22 Upgrade mythwelcome problem

Hello

I have recently upgraded my MythTV FE/BE from 0.21 to 0.22. After the
upgrade everything is working properly except for one thing. My FE/BE is no
longer automatically waking up to record a program. Strangely, it still
wakes up automatically for the daily startup time setting in mythwelcome.
However it fails to start for any scheduled recording

This was all working perfectly prior to the 0.22 upgrade

Does anybody have any idea why this is not working?

Thanks

Jason

--

----------
Dr. Jason But
Lecturer
Centre for Advanced Internet Architectures
Faculty of Information and Communication Technologies
Swinburne University of Technology

Phone: +61 3 9214 4839
Email: jbut [at] swin
www: http://caia.swin.edu.au
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Apr 8, 2010, 6:18 PM

Post #2 of 9 (859 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 04/08/2010 07:37 PM, Jason But wrote:
> I have recently upgraded my MythTV FE/BE from 0.21 to 0.22. After the
> upgrade everything is working properly except for one thing. My FE/BE is no
> longer automatically waking up to record a program. Strangely, it still
> wakes up automatically for the daily startup time setting in mythwelcome.
> However it fails to start for any scheduled recording
>
> This was all working perfectly prior to the 0.22 upgrade
>
> Does anybody have any idea why this is not working?
>

Most of the people who found problems after upgrading from 0.21-fixes
figured out it was a discrepancy between UTC and local time. In theory,
nothing changed in MythTV in that time, and the current
0.22-fixes/0.23-fixes behavior is as desired. However, the kernel or
system may have changed in such a way that you need to modify your
scripts or something.

Also, see http://svn.mythtv.org/trac/ticket/6066 .

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jbut at swin

Apr 8, 2010, 10:24 PM

Post #3 of 9 (848 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 04/09/10 11:18, Michael T. Dean wrote:
> On 04/08/2010 07:37 PM, Jason But wrote:
>> I have recently upgraded my MythTV FE/BE from 0.21 to 0.22. After the
>> upgrade everything is working properly except for one thing. My FE/BE
>> is no
>> longer automatically waking up to record a program. Strangely, it still
>> wakes up automatically for the daily startup time setting in mythwelcome.
>> However it fails to start for any scheduled recording
>>
>> This was all working perfectly prior to the 0.22 upgrade
>>
>> Does anybody have any idea why this is not working?
>>
>
> Most of the people who found problems after upgrading from 0.21-fixes
> figured out it was a discrepancy between UTC and local time. In theory,
> nothing changed in MythTV in that time, and the current
> 0.22-fixes/0.23-fixes behavior is as desired. However, the kernel or
> system may have changed in such a way that you need to modify your
> scripts or something.
>
> Also, see http://svn.mythtv.org/trac/ticket/6066 .
>
> Mike

Thanks Mike

You are correct, my system clock is UTC

I'll have a look over the weekend when I have some time. I don't think there
were any system/time based upgrades during my myth upgrade (I run gentoo and
there weren't an enormous amount of upgrades apart from myth and the
database latin/utf issue).

What I find interesting is that my system still wakes up correctly as per my
2:00am -> 2:30am schedule to download the EPG but fails to wake for the
recorded times.

Like I said, I'll investigate further and see if I can't nail down whether
it is a UTC/localtime issue

Jason

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

sonofzev at iinet

Apr 8, 2010, 11:19 PM

Post #4 of 9 (850 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

>You are correct, my system clock is UTC
>
>I'll have a look over the weekend when I have some time. I don't think there
>were any system/time based upgrades during my myth upgrade (I run gentoo and
>there weren't an enormous amount of upgrades apart from myth and the
>database latin/utf issue).
>
>What I find interesting is that my system still wakes up correctly as per my
>2:00am -> 2:30am schedule to download the EPG but fails to wake for the
>recorded times.
>
>Like I said, I'll investigate further and see if I can't nail down whether
>it is a UTC/localtime issue
>
>Jason
>

Check /etc/conf.d/clock.

This often gets re-written and on late nights after big updates (where there may
be a large number of files to check etc-update) I've often chosed the "-5" option
and not noticed that /etc/conf.d/clock has reverted back to it's original state..
.. which is

clock="UTC"

instead of clock="local"

You may also find your timezone entry looks like TIMEZONE="FACTORY" instead of
"Australia/Melbourne" (or whatever the correct one for you is).....

although you did say there weren't many updates which is a bit weird..

BTW how did you go with mythweb, I'm struggling under Gentoo with this?? (please
see my other posts)..

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jbut at swin

Apr 8, 2010, 11:24 PM

Post #5 of 9 (851 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 04/09/10 16:19, sonofzev [at] iinet wrote:
>> You are correct, my system clock is UTC
>>
>> I'll have a look over the weekend when I have some time. I don't think there
>> were any system/time based upgrades during my myth upgrade (I run gentoo and
>> there weren't an enormous amount of upgrades apart from myth and the
>> database latin/utf issue).
>>
>> What I find interesting is that my system still wakes up correctly as per my
>> 2:00am -> 2:30am schedule to download the EPG but fails to wake for the
>> recorded times.
>>
>> Like I said, I'll investigate further and see if I can't nail down whether
>> it is a UTC/localtime issue
>>
>> Jason
>>
>
> Check /etc/conf.d/clock.
>
> This often gets re-written and on late nights after big updates (where there may
> be a large number of files to check etc-update) I've often chosed the "-5" option
> and not noticed that /etc/conf.d/clock has reverted back to it's original state..
> .. which is
>
> clock="UTC"
>
> instead of clock="local"
>
> You may also find your timezone entry looks like TIMEZONE="FACTORY" instead of
> "Australia/Melbourne" (or whatever the correct one for you is).....
>
> although you did say there weren't many updates which is a bit weird..

Thanks again, will check all this over the weekend

>
> BTW how did you go with mythweb, I'm struggling under Gentoo with this?? (please
> see my other posts)..
>
>
I had no problems after I copied the apache.conf file into the appropriate
directory and restarted apache, it just worked. My myth box is behind my
firewall and only accessible in-house so I have no authentication on it in
case that was an issue. Also, since my mythbox is standalone (not a generic
server),I haven't set up any virtual hosts on it

I only wish I could kick off a mytharchive job from mythweb
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

nospam312 at gmail

Apr 9, 2010, 10:19 AM

Post #6 of 9 (815 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

> I have recently upgraded my MythTV FE/BE from 0.21 to 0.22. After the
> upgrade everything is working properly except for one thing. My FE/BE is no
> longer automatically waking up to record a program. Strangely, it still
> wakes up automatically for the daily startup time setting in mythwelcome.
> However it fails to start for any scheduled recording
> This was all working perfectly prior to the 0.22 upgrade

Also worth checking out http://www.mythtv.org/wiki/ACPI_Wakeup

I updated to a new Mythbuntu and I have the problem where the system
is not waking up - but it does not wake up even using the debug
commands.

Unfortunately it looks like the new Mythbuntu v10.04/Ubuntu may still
not have a high enough kernel to fix the problem being experienced
with these motherboards.

Quoted From URL above:
"Note that kernel version 2.6.26, included in the current Debian
stable distribution, contains a bug that makes ACPI wakeup fail on at
least some motherboards. If this affects you, either upgrade to
2.6.33-rc4 or patch 2.6.26 with this patch"
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jbut at swin

Apr 11, 2010, 3:45 PM

Post #7 of 9 (753 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 04/10/10 03:19, nospam312 wrote:
>> I have recently upgraded my MythTV FE/BE from 0.21 to 0.22. After the
>> upgrade everything is working properly except for one thing. My FE/BE is no
>> longer automatically waking up to record a program. Strangely, it still
>> wakes up automatically for the daily startup time setting in mythwelcome.
>> However it fails to start for any scheduled recording
>> This was all working perfectly prior to the 0.22 upgrade
>
> Also worth checking out http://www.mythtv.org/wiki/ACPI_Wakeup
>
> I updated to a new Mythbuntu and I have the problem where the system
> is not waking up - but it does not wake up even using the debug
> commands.
>
> Unfortunately it looks like the new Mythbuntu v10.04/Ubuntu may still
> not have a high enough kernel to fix the problem being experienced
> with these motherboards.
>
> Quoted From URL above:
> "Note that kernel version 2.6.26, included in the current Debian
> stable distribution, contains a bug that makes ACPI wakeup fail on at
> least some motherboards. If this affects you, either upgrade to
> 2.6.33-rc4 or patch 2.6.26 with this patch"
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

OK, long response follows in case anybody else is searching the lists with a
similar problem.

I checked my clock settings, I run all my systems on UTC time and everything
was correct. I run my own NTP server and my myth box was good so no problem
there.

Then I looked at adding extra debugging to the mythshutdown calls so I added
a (-v most) to the commands in my myth setup and tried again, I also turned
off the regular wakeups for testing purposes.

Now I saw something strange, if I scheduled a recording for the same day as
the day of my test I got

2010-04-10 17:35:24.107 recording scheduled at: 2010-04-10T00:00:00
2010-04-10 17:35:24.117 Scheduled recording time has already passed.
Schedule deleted

If I scheduled a recording for the next day I got

2010-04-10 20:26:42.523 recording scheduled at: 2010-04-11T00:00:00
2010-04-10 20:26:42.531 will wake up at next scheduled program

So it appeared that mythshutdown was changing all the time fields from the
correct time to 00:00:00 while getting the date fields correct.

Then I looked at the mythshutdown source code and noticed nothing
particularly strange. I then checked the contents of the database where the
time is stored and saw that the correct time/date was there (not 00:00:00)

So it appeared that the time was reset to 00:00:00 _after_ mythshutdown
extracted the value from the DB

Finally I did some more googling and eventually stumbled on something, the
wakeup-time format in mythtv-setup needed to be "yyyy-MM-ddThh:mm:ss" but I
had "yyyy-MM-ddThh:mm". I appended the ":ss" and lo and behold, all works
well in the world.

This really should be documented better, it appears that "yyyy-MM-ddThh:mm"
was fine for v0.21 but v0.22 needs the ":ss" or it won't work.

I mentioned earlier that I had not upgraded much but one thing that also
upgraded was the QT libs from v3 to v4. I looked again at the mythshutdown
source and noticed that all time conversions (string<->bin) were managed by
the QT libs. I assume that the QT upgrade suddenly treated time strings that
were missing a "seconds" field to be reset to 00:00:00. A bit of a nasty
gotcha here

So to summarise. People upgrading fro mythtv 0.21 to 0.22 AND using ACPI
auto-wakeup to record stuff NEED to check the "Wakeup time format" field in
the mythtv backend configuration and ensure that seconds are appended to the
end.

On a side issue, I have a recent (2years old) MB on this system and am
running 2.6.30 kernel. I have been unable to get the RTC wakeup to work and
had to resort to the /proc/acpi/alarm as the only means of waking up my
system. I know that /proc/acpi/alram is supposed to be deprecated but
hopefully it will stay in there

Jason
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jstembridge at gmail

Apr 12, 2010, 2:37 AM

Post #8 of 9 (739 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 11 April 2010 23:45, Jason But <jbut [at] swin> wrote:
> Finally I did some more googling and eventually stumbled on something, the
> wakeup-time format in mythtv-setup needed to be "yyyy-MM-ddThh:mm:ss" but I
> had "yyyy-MM-ddThh:mm". I appended the ":ss" and lo and behold, all works
> well in the world.

For what it's worth it *is* mentioned in the documentation

http://www.mythtv.org/wiki/Mythwelcome#Using_MythWelcome.2FMythShutdown_with_ACPI

But I'd agree the current behaviour is certainly unhelpful.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jbut at swin

Apr 12, 2010, 3:35 PM

Post #9 of 9 (723 views)
Permalink

Re: MythTV 0.22 Upgrade mythwelcome problem [In reply to]

On 04/12/10 19:37, James Stembridge wrote:
> On 11 April 2010 23:45, Jason But <jbut [at] swin> wrote:
>> Finally I did some more googling and eventually stumbled on something, the
>> wakeup-time format in mythtv-setup needed to be "yyyy-MM-ddThh:mm:ss" but I
>> had "yyyy-MM-ddThh:mm". I appended the ":ss" and lo and behold, all works
>> well in the world.
>
> For what it's worth it *is* mentioned in the documentation
>
> http://www.mythtv.org/wiki/Mythwelcome#Using_MythWelcome.2FMythShutdown_with_ACPI
>
> But I'd agree the current behaviour is certainly unhelpful.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

True, but no mention for upgrading people who would probably:

1) See no note about the upgrade and think "It worked before so I don't need
to change it"

2) See the web page say hh:mm:ss, look at the screen and see hh:mm and say,
"Yes, that looks correct" without seeing the difference

3) See no obvious error message in the logs saying that time/date is
incorrectly formatted, only that the time is reset to 00:00:00 and only if
they turn on extra debugging

Still I am happy that it is working again, the main point of my spiel was
for people google-searching for similar problems in the future
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads