EPG123 log shows "Time discontinuity detected"

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

EPG123 log shows "Time discontinuity detected"

Post#1 » Wed Sep 20, 2017 2:49 pm

Code: Select all
[9/20/2017 1:15:42 AM] [WARNG] Time discontinuity detected. Service 46525 (KOCEDT2) SH012857740000 (entry 381) ends at 2017-10-02 14:52:00Z, EP026834570007 (entry 382) starts at 2017-10-02 10:00:00Z.
[9/20/2017 1:15:42 AM]         No further discontinuities on KOCEDT2 will be reported for 2017-10-02.
[9/20/2017 1:15:47 AM] [WARNG] Time discontinuity detected. Service 59368 (HBO2HD) SH012857740000 (entry 54) ends at 2017-09-23 05:20:00Z, MV001171630000 (entry 55) starts at 2017-09-23 01:30:00Z.
[9/20/2017 1:15:47 AM]         No further discontinuities on HBO2HD will be reported for 2017-09-23.
[9/20/2017 1:15:57 AM] [WARNG] Time discontinuity detected. Service 63236 (BETHD) SH012857740000 (entry 199) ends at 2017-09-26 06:05:00Z, SH000369550000 (entry 200) starts at 2017-09-26 05:55:00Z.
[9/20/2017 1:15:57 AM]         No further discontinuities on BETHD will be reported for 2017-09-26.
[9/20/2017 1:15:58 AM] [WARNG] Time discontinuity detected. Service 74885 (DJCHHD) SH012857740000 (entry 992) ends at 2017-10-08 19:25:00Z, SH022650030000 (entry 993) starts at 2017-10-08 17:45:00Z.
[9/20/2017 1:15:58 AM]         No further discontinuities on DJCHHD will be reported for 2017-10-08.


Forgot but I think it is just wait it out for SchedulesDirect to fix it or open a ticket with them?
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#2 » Wed Sep 20, 2017 7:07 pm

Yah, I was surprised when I saw this come back as well. rkulagow put in code on his end to check for these discontinuities which meant we never saw them again. I'm thinking that check is no longer working.

If it is currently happening, I would submit a ticket so they can check it out.
User avatar
garyan2
 
Posts: 2197
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 » Wed Sep 20, 2017 7:58 pm

garyan2 wrote:Yah, I was surprised when I saw this come back as well. rkulagow put in code on his end to check for these discontinuities which meant we never saw them again. I'm thinking that check is no longer working.

If it is currently happening, I would submit a ticket so they can check it out.


Should I open a ticket or are you already in contact with rkulagow about this?
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#4 » Wed Sep 27, 2017 2:53 pm

I did not open a ticket with Schedules Direct yet and this error has not returned over the last week but I looked at my trace.log a little more closely today and see the following:

Code: Select all
[9/27/2017 1:15:03 AM] Entering getAllScheduleEntryMd5s() for 21 days on 443 stations.
[9/27/2017 1:15:09 AM] [ INFO] Successfully retrieved Md5s for 443 station's daily schedules.
[9/27/2017 1:15:11 AM] [ INFO] Found 5369 cached daily schedules.
[9/27/2017 1:15:17 AM] [ INFO] Successfully retrieved 439 station's daily schedules.
[9/27/2017 1:15:39 AM] [ INFO] Downloaded 3882 daily schedules.
[9/27/2017 1:16:02 AM] [ INFO] Processed 9251 daily schedules for 443 stations.
[9/27/2017 1:16:02 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.


So it would appear I am not getting data for four stations. Maybe these are the same four stations but how do I confirm which stations these are?

I suppose I should open a ticket with Schedules Direct on this issue but thought I'd post it here in case anyone else is having this issue or know anything pertinent about it that I can pass along to Schedules Direct.

TIA
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#5 » Wed Sep 27, 2017 9:17 pm

You're overthinking a little. Of the 443 stations, only 439 stations had updates needing to be downloaded (successfully retrieved) from SD. So it is possible that 4 of your stations only have 20 days of listings instead of 21 days.
User avatar
garyan2
 
Posts: 2197
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#6 » Thu Sep 28, 2017 11:24 pm

So it's all good then.

Thanks!
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#7 » Mon Oct 16, 2017 2:09 pm

Got a couple more of these..

Code: Select all
[10/15/2017 1:15:28 AM] [WARNG] Time discontinuity detected. Service 57390 (SCIHD) SH012857740000 (entry 248) ends at 2017-10-24 10:08:00Z, SH012531510000 (entry 249) starts at 2017-10-24 08:00:00Z.
[10/15/2017 1:15:28 AM]         No further discontinuities on SCIHD will be reported for 2017-10-24.
[10/15/2017 1:15:29 AM] [WARNG] Time discontinuity detected. Service 67890 (TBSHDP) SH012857740000 (entry 94) ends at 2017-10-18 06:30:00Z, EP009311820123 (entry 95) starts at 2017-10-18 02:30:00Z.
[10/15/2017 1:15:29 AM]         No further discontinuities on TBSHDP will be reported for 2017-10-18.


Code: Select all
[10/16/2017 1:15:32 AM] [WARNG] Time discontinuity detected. Service 67890 (TBSHDP) SH012857740000 (entry 108) ends at 2017-10-19 09:00:00Z, EP005544684488 (entry 109) starts at 2017-10-19 00:00:00Z.
[10/16/2017 1:15:33 AM]         No further discontinuities on TBSHDP will be reported for 2017-10-19.


I'll probably just wait it out and see if it is corrected tonight.
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#8 » Wed Oct 18, 2017 5:09 pm

Submitted a report to Schedules Direct on this on Monday actually. I have not heard back but haven't seen the error again either. Not that it doesn't exist though because epg123 will not tell me after the first instance of the error.
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#9 » Wed Oct 18, 2017 6:27 pm

Sammy2 wrote:Submitted a report to Schedules Direct on this on Monday actually. I have not heard back but haven't seen the error again either. Not that it doesn't exist though because epg123 will not tell me after the first instance of the error.
If you don't get the error, it doesn't exist. EPG123 will only stop reporting errors for that station and that day for that specific update run. It "resets" on next update.
User avatar
garyan2
 
Posts: 2197
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net


Return to EPG123



Who is online

Users browsing this forum: d00zah and 2 guests

cron