Daylight Saving Time change (2007)

[pilotguy7ca]

It must be a Sage server issue since I manually changed the clock back, reset Sage services and it jumps ahead 1 hour. I disabled "sync clock with Sage" and did a reset and it quit jumping.

[pilotguy7ca]

I spoke too soon, it still keeps bumping up my time althought I have sync off, I check the log and it's sage setting my clock anyways???

[clayfree]

I just checked my DirecTivo and the time on the guide is still off by 1 hr. I wonder when it will get corrected, maybe when DST was originally scheduled to start.

[mc2wheels]

This appears to be on the sage servers. I have no problem now that I've turned syncing off. I sure hope my system time doesn't drift too much.

[Homebuilder]

Is there a fix?

I had to back date my computer to fool sage into the right time...

[LazyGun]

I had all the same issues as everyone above. I ran the Java auto update, and it updated me to 1.5.10 (I think), and then I ran the tzdupdate patch. None of this helped. I installed the manual download of java 1.5.11 and rebooted...
Machine came up with the right time. Started Sage. Clock jumped an hour forward.
Turned off Sync with System Clock, restarted sage and service. Clock jumped an hour forward.
I eventually killed the service, closed the UI, and then edited the .properties file by hand, and sync_system_clock was still set to true (I think I actually turned it off 2 or 3 times in the UI.).
So, i changed this to false, saved the file and started the service, and my clock hasn't changed....yet
Hope this helps at least one person...

[Narflex]

IMPORTANT UPDATE

We just fixed this issue on the servers now. We had patched them all ahead of time and it all *should* have been OK. But for some reason the server's had their clock off by an hour. We've now corrected the problem and all clock syncing should work correctly assuming you have the DST fixes on your local machine (the version of Java SageTV ships with is OK for DST, it's 1.4.2_12...although it looks like a new 1.4.2_13 update is needed for Canadian users http://java.sun.com/developer/techni...ml#jdkversion).

The servers are all now running on GMT so this won't happen again on the server end.

Our sincerest apologies for any recordings that were missed due to this.

[kevpriest]

Wow, Sage completely wet the bed when the "real" BSG started. It kept recording, but wouldn't let me see LiveTV, and the recording itself said it stopped at 9:20 (when I reset the clock). I tried cancelling the recording, no go. I tried exiting Sage, no go. I tried killing the task, no go. I had to so a physical reset of the box.

Thanks again, Congress.

[TwistedMelon]

Does anyone know why Sage lists the time as +1 when I have *not* been using the Sync with Server time option? Windows correctly changed the time forward 1 hour and SageTV went forward 2 hours.

I have not been able to get Sage to pick up the correct time yet. I'm running Sage as a service. Have quit, restarted, moved Windows time up and down, etc..

I missed all recordings tonight except 1 and I want to make sure this is fixed by tomorrow night. I'm not really interested in having to set manual recording for all the wrong programs to get what I want.

Bruno

[walter scott]

Originally Posted by kevpriest

Yep, clock just jumped from 9 - 10, so instead of BSG it's recording Dresden Files right now. I changed the clock, but I don't know what's going to happen since the recording already started.

Same here. but just found the messages that explains that it was a server problem. Hey, stuff happens.

[jominor]

Originally Posted by PSUAviator

Agreed. This one lays solely on those who code SageTV. This DST change was in the pipeline for two years. They chose to spend their time on feature creep instead of testing to ensure continuous operation for the users. Don't get me wrong...Sage is a great product, and I extol its virtues to all of my friends... but this was a pretty decent oversight.

When I left home today at 11a... Computer said correct time, SageTV was one hour behind.

When I return at 6p, computer is one hour behind, and Sage behind 2. Seriously? I have the latest version of Java, the MS patch has been installed for months. Everything is working as it should - except for Sage. (I imagine the -1 hour jump this afternoon was due to Sage changing the system clock to coincide with the EPG data)

Why can't we all just use GMT and ignore this? If the Sage folks come back and say it's something to do with the EPG data, I might buy that.

Update: Sun's tzupdater.jar file (mentioned here) seems to have fixed things for me. SageTV's clock and the EPG data have jumped forward, back in sync with the system clock.

SageTV: I, and likely other users, would like to hear some official word on how we'll be affected by the fall DST switch.

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.

[TwistedMelon]

if you didn't hear about the time change until two months ago you've been living under a rock for 2 years. Seriously.

Windows is already a pile of garbage, on top of that Sage is written in Java, might as well be writing it in Perl. No wonder performance on a 3.7Ghz feels like a 200MHz system from 1997.

[Goodspike]

BTW, I heard MSFT was going to change it as it got nearer the deadline, but I don't know if they ever did. Back when I downloaded the Windows DST update, it wasn't a critical update. If they never changed it, you'd have to look for it under the other important updates, or whatever MSFT calls them.

[jominor]

Originally Posted by TwistedMelon

if you didn't hear about the time change until two months ago you've been living under a rock for 2 years. Seriously.

Windows is already a , on top of that Sage is written in Java, might as well be writing it in Perl. No wonder performance on a 3.7Ghz feels like a 200MHz system from 1997.

I correspond with plenty of people and frequent many, many sites daily, so I don't think I was living under a rock.

Windows is fine and so is Java. Anyone who seriously compares Java and Perl is a person with an agenda and people with agendas rarely make good sources of foresight, but excel in hindsight.

[bstowers]

You know, I just want the thing to work, and right now it is not. And I come here trying to find out how to fix it, and I I'm pointed to a thread with 5 pages of posts, mostly with people bickering or adding nothing useful about how to make this stupid thing understand what time it is.

So, here's one more post to add to the noise. Maybe someone will get a clue and put a up a helpful post some place obvious for the next poor slob that comes along.

[rockwella]

yeah seriously...80$ and no support....tsk tsk

[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!

[jkohn]

Originally Posted by Goodspike

BTW, I heard MSFT was going to change it as it got nearer the deadline, but I don't know if they ever did. Back when I downloaded the Windows DST update, it wasn't a critical update. If they never changed it, you'd have to look for it under the other important updates, or whatever MSFT calls them.

No, they pushed it as a critical update quite some time ago. Anybody running Windows XP that didn't have the OS patched for DST is a dork and has no one to blame but themselves (see below )


I guess I got lucky. This past weekend I installed Java 1.6 and SageTV 6.1.4RC on my server and client machines. This morning when I woke up my Sage server had the correct time, even within SageTV. Even the EPG looked fine. My client PC's clock was off by an hour, but that was my fault for having Automatic Updates disabled on that machine and forgetting that I needed to install the DST patch for Windows. Once I installed that and manually corrected the time in the OS, everything was fine on the client too. By the way, I have automatic clock-sync enabled in SageTV.

I had a total of 5 recordings scheduled tonight. I just went through them all, and every one started on time. All but one ended at the correct time, and the one that didn't went 15 minutes over. I guess I can live with that. :smile:

That's pretty incredible that DirectTV still hasn't dealt with this issue given the millions of subscribers they have. My cable-co DVR's were patched a few weeks ago and they handled the DST change without skipping a beat.

[thatdude90210]

At first I did the fix mentioned in this post, but still didn't fix my problem.

Then I did the one in this post, then it finally got the clock set correctly.

Probably had to do them both.

[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?