New to EPG123 and started getting warning

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

New to EPG123 and started getting warning

Post#1 » Mon Jul 10, 2017 2:27 pm

New user so maybe I missed this. The first few days I had no warnings but now I am seeing this in the log:
Code: Select all
[7/10/2017 5:55:59 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 91994 (ACUWTHH) on 2017-07-10 and after.
[7/10/2017 5:56:04 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 102454 (FRT166H) on 2017-07-10 and after.
[7/10/2017 5:56:21 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 74302 (LOOR1983) on 2017-07-10 and after.


What does this mean and should I worry or change anything?
jamestx10
 
Posts: 2
Joined: 5 July 2011

Post#2 » Mon Jul 10, 2017 3:04 pm

This means that Schedules Direct doesn't have information for that channel. You need to open a ticket with them and provide this information in the ticket in addition to your lineup.
Sammy2
 
Posts: 1360
Joined: 24 August 2012
HTPC Specs: Show details

Post#3 » Mon Jul 10, 2017 3:07 pm

This happens periodically and is due to the method Schedules Direct uses to cache the upstream Gracenote data. What the warnings mean for us is those particular stations did not get any updates or additional schedule information. You can open a ticket with SD and basically copy/paste that information In the ticket and it will probably be corrected pretty quickly.

Note that SD is reworking some of their code that would make these errors a thing of the past. I've given it some trial runs and it looks good, so maybe it will be rolled out in the near future. The new method will basically change from SD caching all the data, to a more real-time update from Gracenote to us.
User avatar
garyan2
 
Posts: 2247
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Post#4 » Tue Jul 11, 2017 1:58 pm

Long time EPG123 user. Those errors occur occasionally and are usually due to issues with Schedules Direct data. 95% of the time the issue is fixed within hours... occasionally days. Since I get 21 days of data, it's never an issue for me. The problem gets resolved usually before I knew there was a problem.

For me, if the errors continue for 3-5 days, it could be worth opening a ticket with Schedules Direct. Otherwise, it's a non-issue.
DaveInPa
 
Posts: 67
Joined: 30 October 2015

Post#5 » Tue Jul 11, 2017 2:19 pm

Thanks for the info. Later that day it cleared up
jamestx10
 
Posts: 2
Joined: 5 July 2011

Post#6 » Tue Jul 11, 2017 2:23 pm

DaveInPa wrote:Long time EPG123 user. Those errors occur occasionally and are usually due to issues with Schedules Direct data. 95% of the time the issue is fixed within hours... occasionally days. Since I get 21 days of data, it's never an issue for me. The problem gets resolved usually before I knew there was a problem.

For me, if the errors continue for 3-5 days, it could be worth opening a ticket with Schedules Direct. Otherwise, it's a non-issue.


A new user may not have this luxury. Otherwise, this is very true.
Sammy2
 
Posts: 1360
Joined: 24 August 2012
HTPC Specs: Show details


Return to EPG123



Who is online

Users browsing this forum: Bing [Bot], Yahoo [Bot] and 2 guests

cron