New Warning Message in Trace Log

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 Warning Message in Trace Log

Post#1 » Thu Aug 24, 2017 1:25 am

I have run epg123 V1.1.15 twice. The first time was a couple of days ago. The trace log was normal. Today (8/23) I ran V1.1.15 again and received about 200 warning messages of the following form:

"[8/23/2017 5:06:18 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 10836 (KXLY) on 2017-08-24 and after."

Of course, each warning message was for a different stationid. Since these are classified "warning" messages and since epg123 has not changed since the last run, can I just ignore them and assume that Schedule Direct needs to do something on their end to prevent this. I don't pretend to know what the failure to parse a schedule Md5 means, but I checked 5 of the channels listed in the warning messages and each one has at least 20 days of guide listings. Well beyond the 8/24 date shown in the warning message.
rimmel
 
Posts: 23
Joined: 27 August 2013

Post#2 » Thu Aug 24, 2017 2:03 am

rimmel wrote:I have run epg123 V1.1.15 twice. The first time was a couple of days ago. The trace log was normal. Today (8/23) I ran V1.1.15 again and received about 200 warning messages of the following form:

"[8/23/2017 5:06:18 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 10836 (KXLY) on 2017-08-24 and after."

Of course, each warning message was for a different stationid. Since these are classified "warning" messages and since epg123 has not changed since the last run, can I just ignore them and assume that Schedule Direct needs to do something on their end to prevent this. I don't pretend to know what the failure to parse a schedule Md5 means, but I checked 5 of the channels listed in the warning messages and each one has at least 20 days of guide listings. Well beyond the 8/24 date shown in the warning message.
Those stations with the warnings got no updates. The return message with the schedules from SD were empty. No harm to your guide but you should open a ticket with SD. It is not just you being impacted.
User avatar
garyan2
 
Posts: 2152
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#3 » Thu Aug 24, 2017 5:23 pm

Did this get resolved? I just got wind from Tapatalk that emby users are having what appears to be a related issue. EPG123 just happens to handle it better.
User avatar
garyan2
 
Posts: 2152
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 » Thu Aug 24, 2017 7:37 pm

I will run epg123 again later today and let you know the results.
rimmel
 
Posts: 23
Joined: 27 August 2013

Post#5 » Fri Aug 25, 2017 12:30 am

I ran epg123 again and this time I received about 100 warning messages in the trace log. That is down from about 200 yesterday. Does this signify some progress on SD's part at resolving this issue? Following is a sample warning message from today's run:

[8/24/2017 4:21:02 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 11160 (TMC) on 2017-08-24 and after.

I noticed that the date in the warning message still says "2017-08-24 and after" like yesterday. Also, some of the channels listed in warning messages today did not appear yesterday. So this does not appear to be a simple reduction in the of number channels flagged yesterday. This problem does not appear to be affecting my recordings or the guide in general, yet..
rimmel
 
Posts: 23
Joined: 27 August 2013

Post#6 » Fri Aug 25, 2017 2:54 am

rimmel wrote:I ran epg123 again and this time I received about 100 warning messages in the trace log. That is down from about 200 yesterday. Does this signify some progress on SD's part at resolving this issue? Following is a sample warning message from today's run:

[8/24/2017 4:21:02 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 11160 (TMC) on 2017-08-24 and after.

I noticed that the date in the warning message still says "2017-08-24 and after" like yesterday. Also, some of the channels listed in warning messages today did not appear yesterday. So this does not appear to be a simple reduction in the of number channels flagged yesterday. This problem does not appear to be affecting my recordings or the guide in general, yet..

So it's still going on. I'll capture a Md5 response to show SD what is going on in the message and what is missing. EPG123 recognizes these issues and avoids causing any problems with your guide. Like I said previously, the channels listed in the warnings will not get any updated information. If it continues, those channels will eventually run out of guide listings by simply expiring.

Both runs said 8/24 because the dates being pulled from SD are based on UTC. Your run at 5:06PM on the 23rd was actually 12:06AM UTC on the 24th. The run you just did today was 11:21PM UTC on the 24th as well.
User avatar
garyan2
 
Posts: 2152
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#7 » Fri Aug 25, 2017 4:18 am

Got a response from SD.

rkulagow wrote:Looks like I'm getting bad data from the upstream again; schedules are
being generated that don't contain any program entries. I've opened a
ticket with our upstream to let them know, and to see if they know why
it's happening.

They're on it. The problems we've had in the past on these have usually been resolved pretty quickly.
User avatar
garyan2
 
Posts: 2152
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#8 » Fri Aug 25, 2017 2:41 pm

Looks like this was fixed last night. I just checked your lineup and the errors are no longer there. Your update runs should be clean now.
User avatar
garyan2
 
Posts: 2152
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#9 » Sat Aug 26, 2017 12:09 am

I just completed a run of epg123. All is well! Thanks for all you help on this issue.
rimmel
 
Posts: 23
Joined: 27 August 2013


Return to EPG123



Who is online

Users browsing this forum: No registered users and 1 guest

cron