Page 1 of 2

Re: 2017-06-07: Service disruption

PostPosted: Thu Jun 08, 2017 5:26 pm
by gtb
rkulagow wrote:2017-06-08 @ 04:55P CDT / 21:55 UTC
Our upstream is troubleshooting with their CDN provider and is also putting together an action plan on a work-around to restore service.

Regardless of the outcome (eventually I believe it will be resolved), thank you for keeping us informed, and the constant followup. Would it help if I stand outside their Emeryville office and hold a sign that says "What do we want? Proper EPG. When do we want it? NOW!"

Re: 2017-06-07: Service disruption

PostPosted: Fri Jun 09, 2017 9:55 am
by glenner
I recently setup SageTV v9 to integrate with the SD EPG feed. I setup an SD trial account yesterday to get this working. I have subscribed to the "Toronto OTA" lineup, and am now seeing EPG data for many stations, but am also seeing "No Data" for a few Canadian stations, as well as CW23 (US station).

For example, I see "No Data" for CBLTDT station ID 46245. This is CBC Toronto, channel 5-1.

See screencap. https://drive.google.com/file/d/0B-8Q8P ... BZNDQ/view

Is my SageTV EPG issue related to this "upstream issue"? Is CBC one of the channels affected by this outage? Is there a way to confirm that as I'm trying to determine if my EPG issue is on the SageTV or SD side...

Thanks! -Glenner.

Discussion of 2017-06-07 Service disruption

PostPosted: Fri Jun 09, 2017 11:51 am
by gtb
rkulagow wrote:2017-06-09 @ 10:42A CDT / 15:42 UTC

Some upstream services are beginning to be restored; we will begin testing updates shortly.


Do you have the ability to request a full RFO? And can you share it?

Re: 2017-06-07: Service disruption

PostPosted: Fri Jun 09, 2017 1:54 pm
by rkulagow
Yes, you're affected by the upstream issue, so your lack of data is due to that. You should begin seeing data start to fill in over the next few hours as we begin to catch up.

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Fri Jun 09, 2017 4:29 pm
by GameGod
Is the bad data being returned from the schedules/md5 endpoint also a result of the upstream outage?

The actual issue is documented here: http://forums.schedulesdirect.org/viewtopic.php?f=17&t=2863

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Sat Jun 10, 2017 2:08 pm
by graywolf
Just converted SageTV to Schedules Direct EPG. (Sat 6/10/2017 4pm ET)
The Guide data is good until about 8pm ET Sat 6/17 where I am starting to get sporadic No Data in the guide.
I have data on Sun 6/18 for those channels that did not on the previous day.

Would this be related to this issue?
Will the gaps get automatically filled in once your servers have the correct data?
When might we expect the full data to be available?

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Sat Jun 10, 2017 2:30 pm
by rykr
I'm using tvheadend 4.2 with the tv_grab_sd_json epg grabber and I've been getting errors about invalid schedule data for about 20 or so channels. Could that be due to this service outage?

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Sat Jun 10, 2017 3:45 pm
by gtb
graywolf wrote:Just converted SageTV to Schedules Direct EPG. (Sat 6/10/2017 4pm ET)
The Guide data is good until about 8pm ET Sat 6/17 where I am starting to get sporadic No Data in the guide.
I have data on Sun 6/18 for those channels that did not on the previous day.
Would this be related to this issue?

I am not associated with Schedules Direct (except as a customer), but that is pretty much exactly what you might expect right at the moment (7 days of accurate data, and whatever else might be cached elsewhere with potentially poorer accuracy). Most (properly implemented) solutions should obtain and use additional data when it becomes available.

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Sat Jun 10, 2017 3:59 pm
by gtb
rykr wrote:I'm using tvheadend 4.2 with the tv_grab_sd_json epg grabber and I've been getting errors about invalid schedule data for about 20 or so channels. Could that be due to this service outage?

I would venture the answer is "absolutely". At one point I saw scheduling data that was just not right at all (I suspect the impact may have depended on your particular lineups, and may have depended on exactly what was cached when). The tv_grab_zz_sdjson grabber (the new name for the one you mentioned(*)) was almost certainly trying to do the best it could with what it was given but GIGO. The alternative grabber tv_grab_zz_sdjson_sqlite did not produce any error messages that I saw, but it was certainly limping along with data that was incompletely specified.

(*) You should likely migrate to the new name soonish, as (as I understand it) the old version will be removed in some future distribution.

Re: Discussion of 2017-06-07 Service disruption

PostPosted: Tue Jun 13, 2017 12:55 pm
by colin1951uk
I'm currently getting seven days data for all my channels except one.

The channel is: Front Runner (channel 91 from line up GBR-0001225-DEFAULT)

Is it still on the list please?

Thanks.