Guide Data 1 hour out this morning

[Shane]

Team,

The daylight savings change has gone wrong on the Ice end this morning.

This is evidenced by my Mac Widget & Media Center both being wrong by an hour this morning. As stated in another thread, my machines were patched correctly and handled the Daylight savings extension without an issue, and changed to the correct time themselves overnight.

But now as of this morning everything in the Media Center Guide and everything in the Widget is one hour early.

Can we get an urgent fix today - this seriously impacts the WAF (Wife Approval Factor).

Thanks,
Shane.

[chaosr1]

Same here ???

[dJOS]

Same here, My toppy has the correct time (thanks PBK) and all my PC's have the correct time but the data is out and is causing my timers to be out too!

[dJOS]

I just re-ran TEDS-ICE and the data has been fixed and my toppy EPG & Timers are all correct now.  8)

[Daniel Hall at IceTV]

As djos just said, this has been tested and is now resolved.

Performing a guide fetch will now pull down the correct data.

[dJOS]

Btw Daniel, my ICE-Netgear and another user's ICE-Asus router's are showing DS time still.

[JPP]

Btw Daniel, my ICE-Netgear and another user's ICE-Asus router's are showing DS time still.

And still out now, 3pm.
What's happened to the forum's time stamp btw, it's also way out.

Phil.

[tick007]

As djos just said, this has been tested and is now resolved.

Performing a guide fetch will now pull down the correct data.

Just to follow up on this, last night (around 6:30PM AEST) it seems this still wasn't fixed if pulling the Topfield EPG cache files directly (as opposed to the normal XML files - see below).  Can these cache files be updated as well?  I haven't tried today yet to see if there fixed, but will do so tonight...

Taken from IceGuide4Topfield.log:

02/04/2006 18:23:43 : [Fetch File]Fetch file 20060402_20060402082307_EPG_CACHE.
02/04/2006 18:23:44 : [Fetch File]Fetch file 20060403_20060402082307_EPG_CACHE.
02/04/2006 18:23:45 : [Fetch File]Fetch file 20060404_20060402082307_EPG_CACHE.
02/04/2006 18:23:46 : [Fetch File]Fetch file 20060405_20060402082307_EPG_CACHE.
02/04/2006 18:23:47 : [Fetch File]Fetch file 20060406_20060402082307_EPG_CACHE.
02/04/2006 18:23:48 : [Fetch File]Fetch file 20060407_20060402082307_EPG_CACHE.
02/04/2006 18:23:49 : [Fetch File]Fetch file 20060408_20060402082307_EPG_CACHE.

[Daniel Hall at IceTV]

Just to follow up on this, last night (around 6:30PM AEST) it seems this still wasn't fixed if pulling the Topfield EPG cache files directly (as opposed to the normal XML files - see below).  Can these cache files be updated as well?  I haven't tried today yet to see if there fixed, but will do so tonight...

Taken from IceGuide4Topfield.log:

02/04/2006 18:23:43 : [Fetch File]Fetch file 20060402_20060402082307_EPG_CACHE.
02/04/2006 18:23:44 : [Fetch File]Fetch file 20060403_20060402082307_EPG_CACHE.
02/04/2006 18:23:45 : [Fetch File]Fetch file 20060404_20060402082307_EPG_CACHE.
02/04/2006 18:23:46 : [Fetch File]Fetch file 20060405_20060402082307_EPG_CACHE.
02/04/2006 18:23:47 : [Fetch File]Fetch file 20060406_20060402082307_EPG_CACHE.
02/04/2006 18:23:48 : [Fetch File]Fetch file 20060407_20060402082307_EPG_CACHE.
02/04/2006 18:23:49 : [Fetch File]Fetch file 20060408_20060402082307_EPG_CACHE.

These files themselves look correct, and also have a correct timestamp on them. The "cache" files are actually generated in the instant that you perform a fetch. To go through the filename it is:

DATE OF DATA_DATE AND TIME OF FETCH_EPG_CACHE

So in the above case it was listed at being fetched at 6:23 PM and the files timestamp is then "082307", which being in UTC+10 now is 6:23:07 PM.

When checking on the Topfield what does the data display like?

[tick007]

These files themselves look correct, and also have a correct timestamp on them. The "cache" files are actually generated in the instant that you perform a fetch. To go through the filename it is:

DATE OF DATA_DATE AND TIME OF FETCH_EPG_CACHE

So in the above case it was listed at being fetched at 6:23 PM and the files timestamp is then "082307", which being in UTC+10 now is 6:23:07 PM.

When checking on the Topfield what does the data display like?

Ahh, my mistake.  :)

I'm using JustEPG (v9.2) and it has a hardcoded time offset - I had to set this back to 600 minutes instead of 660 minutes.

Sorry for the confusion.  I was under the impression though that the EPG files above were downloaded direct from icetv instead of downloading the XML and generating locally.  I say this because when I first joined icetv the download log would show the XML files being downloaded and then the cache files being generated, and then one day, it changed to just showing downloading the cache files directly.

So you're saying it still does just download the XML and generate the cache files locally and the log files are now misleading?  It's a different URL than the XML one, and I thought a few months ago I actually  tested it from the command line and it pulled down an EPG cache file... I may have been mistaken, but I'm interested because I'm looking at putting together some command line stuff to run on my Mac so I can finally get my Toppy updated directly (I'm sick of having to plug the laptop in just to do updates  :( )

[Daniel Hall at IceTV]

Ahh, my mistake.  :)

I'm using JustEPG (v9.2) and it has a hardcoded time offset - I had to set this back to 600 minutes instead of 660 minutes.

Sorry for the confusion.  I was under the impression though that the EPG files above were downloaded direct from icetv instead of downloading the XML and generating locally.  I say this because when I first joined icetv the download log would show the XML files being downloaded and then the cache files being generated, and then one day, it changed to just showing downloading the cache files directly.

So you're saying it still does just download the XML and generate the cache files locally and the log files are now misleading?  It's a different URL than the XML one, and I thought a few months ago I actually  tested it from the command line and it pulled down an EPG cache file... I may have been mistaken, but I'm interested because I'm looking at putting together some command line stuff to run on my Mac so I can finally get my Toppy updated directly (I'm sick of having to plug the laptop in just to do updates  :( )

Ahh yes, I had to change JustEPG myself.  :)

Not really, when that URL is hit the cgi program grabs the current data from the database (no real need to into XML and then back out) and formats it in the format for the Topfield. The feed that actually comes down can also contain the latest version of the TAP as well. If looking the raw feed in a browser you will lines that have directory and file information, these are the terminators for each of the cache files with there names, then the file contents is listed.

If you are looking at writing a script for the mac then this feed can be used directly and then used as the terminators of the file. If the current TAP version is sent in the URL as well the TAP will not be downloaded each time.