To be announced

[austin_1100]

Hi,

But of an odd one, all of a sudden some of the channels in media Center have started displaying “To be Annouced”, yet others have retained their listings?

I am fully paid up member of Schedules Direct...

I’m stumped!

Any ideas?

Michael

[garyan2]

Hi,

But of an odd one, all of a sudden some of the channels in media Center have started displaying “To be Annouced”, yet others have retained their listings?

I am fully paid up member of Schedules Direct...

I’m stumped!

Any ideas?

Michael

Gonna need more information.

What version of epg123 are you running, what is the date/timestamp of the epg123.mxf file? Is there anything in the trace.log file?

A "To be Announced" sounds to me like it is stale data and you are not updating. This would probably also mean you are down to maybe a week of guide data. Answering the above questions will confirm/disprove that.

[austin_1100]

Gary,

Thanks for replying so quickly.

So I upgraded to 1.2.4.0 today... I was a little behind - and thought that might be the problem.

The .mxf file was last modified on 08/08/2018 @ 07.52

The trace log has some interesting entries in it:

Code: Select all

16/08/2018 08:25:54] ===============================================================================
[16/08/2018 08:25:54]  Beginning epg123 update execution.
[16/08/2018 08:25:54] ===============================================================================
[16/08/2018 08:25:54] [ INFO] Beginning EPG123 update execution. 2018-08-16 07:25:54Z
[16/08/2018 08:25:54] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: True
[16/08/2018 08:25:55] [ INFO] Token request successful. serverID: 20141201.web.X
[16/08/2018 08:25:56] [ INFO] Status request successful. account expires: 2018-09-12T17:48:39Z , lineups: 4/4 , lastDataUpdate: 2018-08-15T21:21:18Z
[16/08/2018 08:25:56] [ INFO] system status: Online , message: No known issues.
[16/08/2018 08:25:56] [WARNG] epg123 is not up to date. Latest version is 1.2.4 and can be downloaded from http://epg123.garyan2.net.
[16/08/2018 08:25:56] [ INFO] Successfully retrieved TMDb configurations.
[16/08/2018 08:25:56] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[16/08/2018 08:25:56] Entering buildLineupServices() for 4 lineups.
[16/08/2018 08:25:56] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000039-DEFAULT.
[16/08/2018 08:25:58] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000040-DEFAULT.
[16/08/2018 08:25:58] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000449-DEFAULT.
[16/08/2018 08:26:00] [ INFO] Successfully retrieved the station mapping for lineup GBR-1002100-DEFAULT.
[16/08/2018 08:26:00] Exiting buildLineupServices(). SUCCESS.
[16/08/2018 08:26:00] Entering getAllScheduleEntryMd5s() for 14 days on 575 stations.
[16/08/2018 08:26:04] [ INFO] Successfully retrieved Md5s for 575 station's daily schedules.
[16/08/2018 08:26:07] [ INFO] Found 6676 cached daily schedules.
[16/08/2018 08:26:10] [ INFO] Successfully retrieved 575 station's daily schedules.
[16/08/2018 08:26:18] [ INFO] Downloaded 1374 daily schedules.
[16/08/2018 08:26:27] [WARNG] Time discontinuity detected. Service 33635 (HITSRAD) SH012857740000 (entry 91) ends at 2018-08-28 12:00:00Z, SH029899760000 (entry 92) starts at 2018-08-28 00:00:00Z.
[16/08/2018 08:26:27]         No further discontinuities on HITSRAD will be reported for 2018-08-28.
[16/08/2018 08:26:27] [WARNG] Time discontinuity detected. Service 31788 (KERRAD) SH012857740000 (entry 97) ends at 2018-08-28 12:00:00Z, SH016451870000 (entry 98) starts at 2018-08-28 00:00:00Z.
[16/08/2018 08:26:27]         No further discontinuities on KERRAD will be reported for 2018-08-28.
[16/08/2018 08:26:34] [ERROR] Failed to read Md5Schedule file in cache directory.
[16/08/2018 08:26:34] [ERROR] Problem occurred during processMd5ScheduleEntry().
[16/08/2018 08:26:34] [ERROR] Failed to create MXF file. Exiting.
[16/08/2018 08:26:34] [ INFO] epg123 update execution time was 00:00:39.4099082.
[16/08/2018 08:26:34] ===============================================================================
[16/08/2018 08:26:34]  Beginning epg123 client execution.
[16/08/2018 08:26:34] ===============================================================================
[16/08/2018 08:26:34] [ INFO] Beginning epg123 client execution. 2018-08-16 07:26:34Z
[16/08/2018 08:26:34] [ INFO] Import: True , Match: False , NoLogo: False , Force: False , ShowProgress: False
[16/08/2018 08:26:34] [ INFO] epg123 client version: 1.1.19 for Win8.1
[16/08/2018 08:26:36] Entering importMxfFile() for file "C:\epg123\epg123.mxf"
[16/08/2018 08:33:12] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[16/08/2018 08:33:12] Exiting importMxfFile(). SUCCESS.
[16/08/2018 08:33:12] [ INFO] Completed lineup refresh.
[16/08/2018 08:33:12] Entering reindexDatabase()
[16/08/2018 08:33:12] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[16/08/2018 08:33:12] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[16/08/2018 08:33:12] Exiting reindexDatabase(). SUCCESS.
[16/08/2018 08:33:12] [ INFO] Completed EPG123 client execution.
[16/08/2018 08:33:12] [ INFO] EPG123 client execution time was 00:06:38.0870586.
[17/08/2018 06:44:42] ===============================================================================
[17/08/2018 06:44:42]  Beginning epg123 update execution.
[17/08/2018 06:44:42] ===============================================================================
[17/08/2018 06:44:42] [ INFO] Beginning EPG123 update execution. 2018-08-17 05:44:42Z
[17/08/2018 06:44:42] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: True
[17/08/2018 06:44:43] [ INFO] Token request successful. serverID: 20141201.web.X
[17/08/2018 06:44:44] [ INFO] Status request successful. account expires: 2018-09-12T17:48:39Z , lineups: 4/4 , lastDataUpdate: 2018-08-16T19:05:22Z
[17/08/2018 06:44:44] [ INFO] system status: Online , message: No known issues.
[17/08/2018 06:44:44] [WARNG] epg123 is not up to date. Latest version is 1.2.4 and can be downloaded from http://epg123.garyan2.net.
[17/08/2018 06:44:44] [ INFO] Successfully retrieved TMDb configurations.
[17/08/2018 06:44:45] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[17/08/2018 06:44:45] Entering buildLineupServices() for 4 lineups.
[17/08/2018 06:44:45] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000039-DEFAULT.
[17/08/2018 06:44:46] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000040-DEFAULT.
[17/08/2018 06:44:46] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000449-DEFAULT.
[17/08/2018 06:44:48] [ INFO] Successfully retrieved the station mapping for lineup GBR-1002100-DEFAULT.
[17/08/2018 06:44:49] Exiting buildLineupServices(). SUCCESS.
[17/08/2018 06:44:49] Entering getAllScheduleEntryMd5s() for 14 days on 575 stations.
[17/08/2018 06:44:53] [ INFO] Successfully retrieved Md5s for 575 station's daily schedules.
[17/08/2018 06:44:55] [ INFO] Found 5825 cached daily schedules.
[17/08/2018 06:44:59] [ INFO] Successfully retrieved 575 station's daily schedules.
[17/08/2018 06:45:12] [ INFO] Downloaded 2225 daily schedules.
[17/08/2018 06:45:32] [ERROR] Failed to read Md5Schedule file in cache directory.
[17/08/2018 06:45:32] [ERROR] Problem occurred during processMd5ScheduleEntry().
[17/08/2018 06:45:32] [ERROR] Failed to create MXF file. Exiting.
[17/08/2018 06:45:32] [ INFO] epg123 update execution time was 00:00:50.2214294.
[17/08/2018 06:45:33] ===============================================================================
[17/08/2018 06:45:33]  Beginning epg123 client execution.
[17/08/2018 06:45:33] ===============================================================================
[17/08/2018 06:45:33] [ INFO] Beginning epg123 client execution. 2018-08-17 05:45:33Z
[17/08/2018 06:45:33] [ INFO] Import: True , Match: False , NoLogo: False , Force: False , ShowProgress: False
[17/08/2018 06:45:33] [ INFO] epg123 client version: 1.1.19 for Win8.1
[17/08/2018 06:45:34] Entering importMxfFile() for file "C:\epg123\epg123.mxf"
[17/08/2018 06:48:56] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[17/08/2018 06:48:56] Exiting importMxfFile(). SUCCESS.
[17/08/2018 06:48:56] [ INFO] Completed lineup refresh.
[17/08/2018 06:48:56] Entering reindexDatabase()
[17/08/2018 06:48:56] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[17/08/2018 06:48:56] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[17/08/2018 06:48:56] Exiting reindexDatabase(). SUCCESS.
[17/08/2018 06:48:56] [ INFO] Completed EPG123 client execution.
[17/08/2018 06:48:56] [ INFO] EPG123 client execution time was 00:03:22.7336888.
[18/08/2018 00:00:01] ===============================================================================
[18/08/2018 00:00:01]  Beginning epg123 update execution.
[18/08/2018 00:00:01] ===============================================================================
[18/08/2018 00:00:01] [ INFO] Beginning EPG123 update execution. 2018-08-17 23:00:01Z
[18/08/2018 00:00:01] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: True
[18/08/2018 00:00:02] [ INFO] Token request successful. serverID: 20141201.web.X
[18/08/2018 00:00:02] [ INFO] Status request successful. account expires: 2018-09-12T17:48:39Z , lineups: 4/4 , lastDataUpdate: 2018-08-17T13:42:39Z
[18/08/2018 00:00:02] [ INFO] system status: Online , message: No known issues.
[18/08/2018 00:00:02] [WARNG] epg123 is not up to date. Latest version is 1.2.4 and can be downloaded from http://epg123.garyan2.net.
[18/08/2018 00:00:03] [ INFO] Successfully retrieved TMDb configurations.
[18/08/2018 00:00:03] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[18/08/2018 00:00:03] Entering buildLineupServices() for 4 lineups.
[18/08/2018 00:00:03] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000039-DEFAULT.
[18/08/2018 00:00:04] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000040-DEFAULT.
[18/08/2018 00:00:06] [ INFO] Successfully retrieved the station mapping for lineup GBR-1000449-DEFAULT.
[18/08/2018 00:00:08] [ INFO] Successfully retrieved the station mapping for lineup GBR-1002100-DEFAULT.
[18/08/2018 00:00:09] Exiting buildLineupServices(). SUCCESS.
[18/08/2018 00:00:09] Entering getAllScheduleEntryMd5s() for 14 days on 575 stations.
[18/08/2018 00:00:13] [ INFO] Successfully retrieved Md5s for 575 station's daily schedules.
[18/08/2018 00:00:15] [ INFO] Found 6777 cached daily schedules.
[18/08/2018 00:00:17] [ INFO] Successfully retrieved 298 station's daily schedules.
[18/08/2018 00:00:24] [ INFO] Downloaded 1273 daily schedules.
[18/08/2018 00:00:29] [WARNG] Time discontinuity detected. Service 103634 (KEEPIC) SH012857740000 (entry 352) ends at 2018-08-29 08:00:00Z, SH028564960000 (entry 353) starts at 2018-08-29 00:00:00Z.
[18/08/2018 00:00:29]         No further discontinuities on KEEPIC will be reported for 2018-08-29.
[18/08/2018 00:00:39] [WARNG] Time discontinuity detected. Service 33635 (HITSRAD) SH012857740000 (entry 99) ends at 2018-08-30 12:00:00Z, SH029899760000 (entry 100) starts at 2018-08-30 00:00:00Z.
[18/08/2018 00:00:39]         No further discontinuities on HITSRAD will be reported for 2018-08-30.
[18/08/2018 00:00:49] [ERROR] Failed to read Md5Schedule file in cache directory.
[18/08/2018 00:00:49] [ERROR] Problem occurred during processMd5ScheduleEntry().
[18/08/2018 00:00:49] [ERROR] Failed to create MXF file. Exiting.
[18/08/2018 00:00:49] [ INFO] epg123 update execution time was 00:00:48.4042158.

But not sure what it all means?

Thanks,

Michael

[garyan2]

Looks like you have a corrupted file in your cache. Open the EPG123 Configuration GUI, click the [Clear Cache] button, and when it completes, click the [Save & Execute] button. That should do it.

[Space]

I'm wondering if it would be possible for EPG123 to delete cache files that it is unable to read successfully and then re-download fresh data (which will rebuild that cache file). Or perhaps it is more complicated than that.

[garyan2]

I'm wondering if it would be possible for EPG123 to delete cache files that it is unable to read successfully and then re-download fresh data (which will rebuild that cache file). Or perhaps it is more complicated than that.

I was just looking at that. Now that EPG123 has a status logo (if used), I may just do that. If there is a problem with the file, then epg123 can delete the offending file and just not update that channel on that day. It won't be until the next update that it will be downloaded again, but the problem file will be cleared.

[Space]

I'm wondering if it would be possible for EPG123 to delete cache files that it is unable to read successfully and then re-download fresh data (which will rebuild that cache file). Or perhaps it is more complicated than that.

I was just looking at that. Now that EPG123 has a status logo (if used), I may just do that. If there is a problem with the file, then epg123 can delete the offending file and just not update that channel on that day. It won't be until the next update that it will be downloaded again, but the problem file will be cleared.

Definitely seems like a better option than aborting the entire MXF file generation.

Another option is to delete the bad cache file and continue (deleting any other corrupt cache files it finds along the way) and then at the end of the process, if it had found/deleted any cache files, just restart the MXF file generation right away. This way you don't go an extra day without updating the channels that had corrupted data.

I would limit this to only 1 retry, as if there is still corruption after the second pass, then you probably have bigger problems.

[garyan2]

Definitely seems like a better option than aborting the entire MXF file generation.

Another option is to delete the bad cache file and continue (deleting any other corrupt cache files it finds along the way) and then at the end of the process, if it had found/deleted any cache files, just restart the MXF file generation right away. This way you don't go an extra day without updating the channels that had corrupted data.

I would limit this to only 1 retry, as if there is still corruption after the second pass, then you probably have bigger problems.

Aborting the entire update was on purpose. It was not easy to notice when a single station out of 500 was not getting updated; It was much easier to notice when the entire guide was not getting updated. Now with the status logo, it is very easy to be aware of both cases.

Sorry, no loops or retries... just not going to happen if I want to keep my sanity. There is just too many balls up in the air that would have to be reset and tracked to do this without much gain. The errors in the file(s) would most likely be coming from the source (SD) which means it is probably from the last day of the request (i.e. day 14 from a 14-day update). Waiting a day for the file to be downloaded on next update means for 1 day, that station only had 13 days of listings as opposed to the 14 all other stations had. The ROI is very small.

[Space]

Definitely seems like a better option than aborting the entire MXF file generation.

Another option is to delete the bad cache file and continue (deleting any other corrupt cache files it finds along the way) and then at the end of the process, if it had found/deleted any cache files, just restart the MXF file generation right away. This way you don't go an extra day without updating the channels that had corrupted data.

I would limit this to only 1 retry, as if there is still corruption after the second pass, then you probably have bigger problems.

...

Sorry, no loops or retries... just not going to happen if I want to keep my sanity. There is just too many beans up in the air that would have to be reset and tracked to do this without much gain. The errors in the file(s) would most likely be coming from the source (SD) which means it is probably from the last day of the request (i.e. day 14 from a 14-day update). Waiting a day for the file to be downloaded on next update means for 1 day, that station only had 13 days of listings as opposed to the 14 all other stations had. The ROI is very small.

I didn't realize the corruption came from the source, I guess in that case retrying right away doesn't make sense since it would likely re-download the same corrupted listings. Although unless the problem is corrected at the source, I would expect it to have the same problem the following day as well, although I don't know what type of corruption it is, and it may very well be corrected the next day.

[austin_1100]

Well the rebuild worked...

Just wondered if there was something dead simple that could be done to tell someone what they need to do..

I’ve evening running epg123 for 12 months without issue, love the way I can customise the guide and the way everything just works.

Just wonder if when I went into the GUI there could have been something that perhaps said “cache error”

I’m not a programming expert, and I accept it’s probably not that easy, but just a small status box with some troubleshooting status would be ace!

Regards,

Michael

[austin_1100]

So tonight... To be annouced reappeared!! Aghhhhh!!!!

I have cleared the cache again, saved & executed, and then thought I’d recreate the update task...

Let’s see how it goes...

Not sure why this has suddenly started happening

Regards,

Michael

[garyan2]

Now it sounds like you were importing the wrong file. When you did a Save & Execute it worked, but the scheduled task imported an old file... your scheduled task is now the culprit. When you upgraded to 1.2.4.0, did you delete and create a new task?

[austin_1100]

Now it sounds like you were importing the wrong file. When you did a Save & Execute it worked, but the scheduled task imported an old file... your scheduled task is now the culprit. When you upgraded to 1.2.4.0, did you delete and create a new task?

No I forgot! All because I VNC'd to the machine (I use a Media Centre PC and XBOX 360's to share TV throughout the house).

Fingers crossed with the recreation of the task it'll sort it out

Regards,

Michael