Discussion of 2017-06-07 Service disruption

Re: 2017-06-07: Service disruption

Postby gtb » Thu Jun 08, 2017 5:26 pm

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!"
gtb
 
Posts: 62
Joined: Thu Oct 02, 2014 2:07 pm

Re: 2017-06-07: Service disruption

Postby glenner » Fri Jun 09, 2017 9:55 am

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.
Server: Lenovo M910 Tiny (i5-7500T), Win10Pro, 32GB RAM, 512 SSD, 6 HDD (8TB total), HDHR Dual Tuner (HDHR-US), HDHR Extend (HDTC-2US), CM 4221/7778
Software: SageTV v9.1.2.662, SageMC/Foofaraw theme (high WAF), SD EPG
Clients: 3 x HD300
glenner
 
Posts: 1
Joined: Fri Jun 09, 2017 9:33 am

Discussion of 2017-06-07 Service disruption

Postby gtb » Fri Jun 09, 2017 11:51 am

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?
gtb
 
Posts: 62
Joined: Thu Oct 02, 2014 2:07 pm

Re: 2017-06-07: Service disruption

Postby rkulagow » Fri Jun 09, 2017 1:54 pm

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.
rkulagow
SD Staff
 
Posts: 884
Joined: Tue Aug 14, 2007 3:15 pm

Re: Discussion of 2017-06-07 Service disruption

Postby GameGod » Fri Jun 09, 2017 4:29 pm

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
GameGod
 
Posts: 58
Joined: Fri Aug 17, 2007 12:26 pm

Re: Discussion of 2017-06-07 Service disruption

Postby graywolf » Sat Jun 10, 2017 2:08 pm

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?
graywolf
 
Posts: 5
Joined: Sun May 28, 2017 3:16 pm

Re: Discussion of 2017-06-07 Service disruption

Postby rykr » Sat Jun 10, 2017 2:30 pm

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?
rykr
 
Posts: 3
Joined: Sat Jun 10, 2017 6:21 am

Re: Discussion of 2017-06-07 Service disruption

Postby gtb » Sat Jun 10, 2017 3:45 pm

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.
gtb
 
Posts: 62
Joined: Thu Oct 02, 2014 2:07 pm

Re: Discussion of 2017-06-07 Service disruption

Postby gtb » Sat Jun 10, 2017 3:59 pm

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.
gtb
 
Posts: 62
Joined: Thu Oct 02, 2014 2:07 pm

Re: Discussion of 2017-06-07 Service disruption

Postby colin1951uk » Tue Jun 13, 2017 12:55 pm

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.
colin1951uk
 
Posts: 5
Joined: Sun May 22, 2016 9:08 am

Next

Return to Service Issues

Who is online

Users browsing this forum: No registered users and 1 guest

cron