SageTV EPG Server Update

[dkardatzke]

As many of you noticed, our server was down for a few hours late thursday night into Friday morning. When it was brought back up Friday the time was incorrect which may have caused anyone who had an EPG update between 8am and 12am PST Friday to be off by one hour and a few minutes. We apologize for any inconvenience or missed recordings this may have cause.

The time will be corrected again on your next EPG update or if you would like to force an update, go into Setup > Channel Setup and just enable or disable a channel to force an update. As a reference for the future, we do have protective measures on the server that updates the time automatically on a daily basis so this would have corrected on its own if it went unnoticed. If you have any questions about correcting your time, please let us know.

Dan

[Opus4]

Originally posted by dkardatzke
As a reference for the future, we do have protective measures on the server that updates the time automatically on a daily basis so this would have corrected on its own if it went unnoticed.

Just a suggestion... instead of having it update on a daily basis, perhaps install a utility that will check the time more frequently. If it updated itself every few minutes (hourly? half-hourly?), very few people would have been affected.

- Andy

[stanger89]

And how about a feature request for future versions of SageTV.

Add a maximum clock update so that if Sage syncs with the server and has to adjust the clock more than say 30 minutes (maybe as a configureable property clock_max_update=) Sage will pop up a confirmation dialog asking if it is OK to update the clock to x:xx.

[SHS]

That sound like super cool idea stanger89
But I perf Automatic setting

[stanger89]

Well, my idea is that 99.99% of the time your PC clock isn't off my more than a few seconds, maybe a minute, so under normal circumstances Sage just update the clock in the background, but if Sage were to go sync the clock and see that it was of by an hour it would ask before changing it.

Of course there could probably be some mechanism to automatically adjust for DST.

[Opus4]

Originally posted by stanger89
Of course there could probably be some mechanism to automatically adjust for DST.

Windows can easily do that w/o having it (Windows) set to automatically update the time every day... of course, that could still leave the issue of what SageTV will do when it notices that happen. Plus, some areas don't change the time for DST.

- Andy

[stanger89]

That's one thing I'm not entirely sure about. I don't think Sage wories about time-zones or DST, I think internaly it just uses GMT and then converts to your local time for display. It seems that way because some people were commenting that the Sage time and EPG time were off by an hour, but that everything worked ok (meaning recordings were recorded at the correct time). So it may not be necessary to worry about DST.

[Opus4]

That was part of the problem -- several people reported that their recordings were off by an hour too & the PC clock was off.

- Andy

[stanger89]

Yeah, this time the there was an error in the time, but some of the earlier problems were just local time zone setting problems that didn't seem to affect the performance.

[Opus4]

That may have been related to whether they had SageTV sync their system clock or not, I'm guessing.

- Andy

[cmaffia]

On my network I use the Windows Time Service.
Didn't want to use the default XP service because it connects to M$.
I configured the service to check and syncronize every hour.
This works like a charm in terms of guide data. :-)