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: 25
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: 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#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: 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 » Thu Aug 24, 2017 7:37 pm

I will run epg123 again later today and let you know the results.
rimmel
 
Posts: 25
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: 25
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: 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#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: 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#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: 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#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: 25
Joined: 27 August 2013

Post#10 » Thu Oct 19, 2017 12:08 am

On the latest run of epg123 [10/17/2017] I received many of the warning messages in the trace log regarding failure to parse schedule md5. Last time this happened was mid August. Is SD having upstream problems again? Are others seeing these warning message? If this persists I'll open an SD ticket. By the way I have also seen some time discontinuity messages in the last week.
rimmel
 
Posts: 25
Joined: 27 August 2013

Post#11 » Thu Oct 19, 2017 4:58 pm

In my trace log, I am getting many of these:
[ERROR] Did not find expected Md5Schedule file in cache directory. 200 + entries
Failed to parse the schedule Md5 return for stationId .... A few Entries
[WARNG] Time discontinuity detected. Service 45654 (ESPNU) SH012857740000 (entry 38) ends at 2017-10-22 03:00:00Z, SH013254680000 (entry 39) starts at 2017-10-22 02:00:00Z. Several many of these.

I also have noticed that sports (NFL) guide entrys are saying team TBD and never get updated even as the games have started.

Background, I am currently using lineup USA-OH34511-X. But... I just switched from a TWC/Insight to a Spectrum plan. But, I have not changed the lineup because it is still on the old Insight infrastructure. All I got was higher speed Internet and more channels for $9 more. :-)

Thoughts?

Randyo
User avatar
Randyored
 
Posts: 16
Joined: 23 April 2013

Post#12 » Thu Oct 19, 2017 5:09 pm

Anyone experiencing these discontinuities and/or MD5 errors ("did not find" due to MD5 mismatch or "failed to parse" due to missing data) need to submit a ticket with SD. Looks like they may be having an upstream problem again.
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#13 » Thu Oct 19, 2017 5:22 pm

I have submitted an SD ticket. Will let you know when they respond with details.
User avatar
Randyored
 
Posts: 16
Joined: 23 April 2013

Post#14 » Thu Oct 19, 2017 6:00 pm

I'm seeing the same thing. Will also submit a ticket.
stuartm
 
Posts: 329
Joined: 5 November 2012
Location: Longmont, CO
HTPC Specs: Show details

Post#15 » Thu Oct 19, 2017 7:43 pm

Likewise, I got a failure last night:

[10/19/2017 4:11:57 AM] [ INFO] Downloaded 2613 daily schedules.
[10/19/2017 4:11:58 AM] [WARNG] Time discontinuity detected. Service 10150 (COMEDYP) SH012857740000 (entry 402) ends at 2017-10-28 12:25:00Z, MV005581230000 (entry 403) starts at 2017-10-28 08:35:00Z.
[10/19/2017 4:11:58 AM] No further discontinuities on COMEDYP will be reported for 2017-10-28.
[10/19/2017 4:11:58 AM] [ERROR] Did not find expected Md5Schedule file in cache directory.

Does that mean, for ticket purposes, that the "expected Md5Schedule file" is for COMEDYP? Nothing else is identified.
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#16 » Thu Oct 19, 2017 8:37 pm

webminster wrote:Does that mean, for ticket purposes, that the "expected Md5Schedule file" is for COMEDYP? Nothing else is identified.

Unfortunately, the "expected Md5Schedule file" is for an unknown station; not necessarily for COMEDYP. EPG123 doesn't track which Md5 belongs to which station or which date ... it finds out when it opens the cached file. That cant happen when the file doesn't exist. I'll look into finding a way to track this information in code for a future release.
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#17 » Fri Oct 20, 2017 12:18 am

Sort of the problem. I opened a ticket with Robert re: the time discontinuity and missing file, of course he asked what file was missing. No way I can answer that question. So since the creation failed on a missing file and no way to know which or why... what to do other than wait and see if the problem cures itself?
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#18 » Fri Oct 20, 2017 12:54 am

I had what seems to be a million "[ERROR] Did not find expected Md5Schedule file in cache directory" errors in my trace.log this morning, to many to cut and paste into a code box. My manual run worked fine but what's going on lately?
Sammy2
 
Posts: 1360
Joined: 24 August 2012
HTPC Specs: Show details

Post#19 » Fri Oct 20, 2017 3:03 am

I also ran a manual run and it did not produce any errors. I had one [WARNG] Failed to parse the schedule Md5 return for stationId.

Randyo
User avatar
Randyored
 
Posts: 16
Joined: 23 April 2013

Post#20 » Fri Oct 20, 2017 4:58 am

webminster wrote:Sort of the problem. I opened a ticket with Robert re: the time discontinuity and missing file, of course he asked what file was missing. No way I can answer that question. So since the creation failed on a missing file and no way to know which or why... what to do other than wait and see if the problem cures itself?

What version are you running? I think in 1.1.17 I allowed it to proceed with creating the mxf file with these errors ... it would just have gaps in the update but your existing data in the database for those gaps would still be there.
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

Next

Return to EPG123



Who is online

Users browsing this forum: No registered users and 1 guest

cron