Daylight Saving Time change (2007)

[Opus4]

The forum-wide announcement about this issue has been updated with the following 2 points:

• The link to the post containing a list of up-to-date java versions has been updated.
• A note from SageTV about the EPG server time fix is here. Note that because MANY people's SageTV systems will be trying to connect for EPG updates, it may take longer than normal for your update to complete.

----

If Windows is up to date and java is now up to date on your PC, yet the time on your system got reset when it synced with the EPG server, you should be able to update your EPG data and get the time set correctly now.

There are a lot of SageTV systems trying to get EPG updates. Due to this heavy EPG server load at the moment... if this EPG update + clock sync does not work, you can try disabling the "sync the system clock with the SageTV server" option (found in Detailed Setup -> General) and then setting your system time your self or via another time utility. You can reset that option later if you wish, once the EPG server load has returned to normal over the next day or so.

- Andy

[stevech]

Originally Posted by avonnied

argg my clock is also wrong....



so if i uncheck sync time, how do i set sage time manually?

this is retarded that it just doesn't read what the server time is set at..

doesn't java just get its time from the system? (hence why it changes back and forth)..


is there anyway to fix this with out having to do installations of a new java or what not?

Java does NOT use MS Windows time zone info but it should. SageTV uses the Java VM.

Earlier in this thread are USER-POSTED instructions on how to download Sun's patch to Java Run-time Environment (JRE) aka the VM. It's called tzupdate.jar. This procedure is a major pain in the arse - should have been automated by Sage.

No need to load a whole new Java release.

Of course, you'll need the MS WIndows patch too, if you didn't do that already, or get it via auto-update.

The instruction to (manually) update your Guide data after getting the time patches: The only way I know of is to go to Sage's setup for the channel choices you have for your tuner. Click to turn off, then on again, one of the green dots, then exit out. This is the hack way to force the guide to be re-read.

[nielm]

According to the linked KB article at the top of this thread, MSFT only released their update to Windows at the beginning of February. This is incredibly late IMHO. The versions of Java that included fixed TZ rules had been released many months previously...


OT: While none of this affects me being on the other side of the Atlantic, I cannot believe that the US congress are messing around with DST! the impact on organisations as well as individuals must be huge: some estimates reckon $2bn! And the reason: energy saving?! so instead of burning your lights at night for, what 3 weeks?, you burn them in the morning...

[hemicuda]

Originally Posted by nielm

OT: I cannot believe that the US congress are messing around with DST!

typical BS we deal w/ on a daily basis "Common Sense" died decades ago preceded by "Horse Sense" and "the good sense God gave a goose to fly backwards." Ok, that last one is REALLY old; blame my granny for it.

I'm just thankful that all my PCs (about 8 total) made it through the new DST. Now we're just waiting for the Sage server(s) to catch up.

[jominor]

Originally Posted by nielm

According to the linked KB article at the top of this thread, MSFT only released their update to Windows at the beginning of February. This is incredibly late IMHO. The versions of Java that included fixed TZ rules had been released many months previously...


OT: While none of this affects me being on the other side of the Atlantic, I cannot believe that the US congress are messing around with DST! the impact on organisations as well as individuals must be huge: some estimates reckon $2bn! And the reason: energy saving?! so instead of burning your lights at night for, what 3 weeks?, you burn them in the morning...

Apparantly MS, Oracle, Sun, etc were all living under rocks because no one seemed to know this thing was coming. Or all these companies decided to wait until this year (its only March) because none of them issued patches in 05 or 06.

[Goodspike]

Originally Posted by stevech

Earlier in this thread are USER-POSTED instructions on how to download Sun's patch to Java Run-time Environment (JRE) aka the VM. It's called tzupdate.jar. This procedure is a major pain in the arse - should have been automated by Sage.

No need to load a whole new Java release.

So you're recommending people do something that's a major PITA, over doing something that's simple?

Personally I'd been waiting for 1.6 to go non-beta, and apparently it has, so I'd have been updating Java anyway. I'm not terribly concerned about security issues on my HTPC, but using an ancient version of Java just to get Sage to work reliably had always bothered me. So far, Sage has been rock solid with 1.6.

So . . . I'd recommend doing that over updating an older version.

[Goodspike]

Originally Posted by nielm

According to the linked KB article at the top of this thread, MSFT only released their update to Windows at the beginning of February. This is incredibly late IMHO. The versions of Java that included fixed TZ rules had been released many months previously...

I'm pretty sure it was available before that as an optional update--and probably became a critical update in February.

[flavius]

Make sure to check your server time. After applying all the patches on Sunday morning, the server was fine all day - only to switch back on hour around 9pm that day and royally screwing with my Sunday evening recordings.

[Opus4]

Originally Posted by flavius

Make sure to check your server time. After applying all the patches on Sunday morning, the server was fine all day - only to switch back on hour around 9pm that day and royally screwing with my Sunday evening recordings.

In case you missed it, that issue on the EPG server should have been resolved here. I added a comment about updating the time here.

- Andy

[FidgetyRat]

I tried a downloadable update rather then use windows-update. That didn't work out too well. Got home and the server didn't adjust.

Stupid windows.

The last thing I want to do on my HTPC is open IE


I guess the moral of the story. Don't trust 3rd party timezone patches.

[flavius]

Thanks, Andy,

I guess, I can stop checking server time, now. Fortunately, everything I missed has reruns today.

[gndprx]

I was fine all day until around 9pm at which point my Sunday viewing went down the tubes. Locked up in the middle of watching the playback of Family guy and I wasn't able to get back to Live TV as mentioned elsewhere in this thread. Missed all of the shows between 9 and 10 and anything that started recording until I fixed the problem. Not a big deal, just annoying for the WAF.

Once I applied the J2RE 1_4_2_14 (I was previously on 1_4_2_04) everything seemed to be ok after a reboot. My times went back to normal and it even got a little quicker which I'm assuming was a side effect of the java update.

Just wanted to post my results...yours may vary.

[matt91]

So despite having Java JRE 1.6.0, my sage EPG has been off one hour since yesterday. I assumed that since 1.6.0 was newer than 1.4.2, I was all set.

Not true - as soon as I applied the tzupdater and forced an EPG eupdate, my sage EPG is back to normal.

Thanks for the helpful hints here!

matt

[ChePazzo]

Now that I think about it, this doesn't make any sense that updating Java would change my system clock . . . .

Originally Posted by ChePazzo

So, after watching some TV my wife saw the time on the SageTV and said, "Is it really that late?" so I checked every clock in my house as well as the cell and realized that sage was +1hr (this was 11:30pm EDT).

I have set to sync with sage for time, but I guess that didn't really do it.

So, I reinstalled Java:

SAGESERVER ~ # date
Mon Mar 12 01:05:34 EDT 2007

SAGESERVER ~ #emerge --pretend jre
[ebuild Rf ] dev-java/sun-jre-bin-1.5.0.06

SAGESERVER ~ # date
Mon Mar 12 00:09:27 EDT 2007

Not sure how reinstalling the same version of java fixed anything, though. Perhaps I just needed to restart things.

Strange because I just finished building this system yesterday!

[rbrown3]

One question:

What happens to cause your SageTV system to be *one hour ahead*???

On the morning of 3/11, my SageTV installation showed the correct time (correct time in DST). Unfortunately, between around 5:00PM and 9:00 PM (when I was scheduled to start recording things) it actually went 1 hour ahead!

At approximately 1:31 DST, I set my Windows system clock back (to Eastern time!), thinking that that would correct the problem. It appeared to (though reading this forum I now know that SageTV does not use Windows system clock). But by the time I came back from work, SageTV was 1 hour ahead again!

Has anyone else seen this problem? It is looking to me as if the JVM Version I have (J2SE V5.0 update 7) is actually *overcompensating* for the time zone change! I can't seem to make it stop doing this.

Someone please advise...

[flavius]

See Opus4's post above.

[cslatt]

Originally Posted by rbrown3

One question:

What happens to cause your SageTV system to be *one hour ahead*???

Installing the latest version of Java 6 and rebooting fixed it for me.

http://java.sun.com/javase/6/

[PSUAviator]

I'll drink to that. Daylight Savings is a ridiculous practice, though I do enjoy having more sunlight after work.

It seems that SageTV may not have tested their system properly. They're to be commended for promptly correcting the problem and, just as important, admitting their error.

Originally Posted by jominor

Quite a few of us didn't even hear about this until maybe one or two months ago. Congress didn't exactly consult us. So all my normal developer tasks have to be done in addition to applying patches and testing.

I don't blame Sage. Blame your Congress.

[walter scott]

Originally Posted by PSUAviator

I'll drink to that. Daylight Savings is a ridiculous practice, though I do enjoy having more sunlight after work.

It seems that SageTV may not have tested their system properly. They're to be commended for promptly correcting the problem and, just as important, admitting their error.

I do hate DST, bur I do agree that Sage is to be commended for admitting they had a problem. good for them. i think sage support does a decent job.

[ausm]

Originally Posted by malore

I joined the ranks of those with the SageTV's clock being off by an hour this morning. Before DST started I saw that the scheduled recordings were off by an hour so a show that should be from 9-10 was listed as 8-9. So I was expecting trouble.

By looking at the running programs, I determined that SageTV was using windows\system32\java.exe
So, I opened a command prompt at that location and executed "java -version" and was shown 1.4.2...
I then exited SageTV and downloaded and installed the current version of Java from http://www.java.com/en/download/manual.jsp
I then checked the version of Java and this time it was 1.5.0_11-b03
I fired up SageTV and everything is back to normal.

Now hopefully the new version of Java won't mess anything up, so I don't have to dig through the debates about the best version of Java to use.

I am curious that even though this thread is sticky, I don't really see much in the way of an official response. TiVo on the other hand, sent me both an email and an onscreen message detailing what to expect.

Thx a million Malore! I narrowed it the problem down to Sage TV 5.0 but I was at a loss on how to fix it. Your advice rectified the problem.