Re: 2017-06-07: Schedules Direct service issue
Posted: Fri Jun 16, 2017 6:12 pm
Still 7 days for me. I never lost my line up though.
The Best Place To Come For All Your Windows Media Center Needs
https://www.thegreenbutton.tv/forums/
Re: 2017-06-07: Service disruption
Postby rkulagow » Fri Jun 16, 2017 9:15 am
2017-06-16 @ 1:10P / 16:10 UTC
We have found an issue with some responses from our upstream; stations which are valid aren't returning data and are delaying processing because the null response is different than previous null responses, so our code was in an infinite retry loop. Code has been added to break out of the loop and we have notified our upstream of the stations which are causing the problem.
We will be increasing our upstream fetch quantity later today to restore 14+ days of schedule.
Just did the math for my 5:01 AM EDT (so, circa 21st century Zulu time... OK, 9:01 ) scheduled update and got 20.9+ days for my configured 21 days. That's for Comcast Digital in my area. Data starts to drop off the evening of July 7, so it's looking good on my end.garyan2 wrote:Looks like we are holding steady at 13 days of data right now. SD is taking measured steps in building everything back up to the 21 days we are used to.
I thought I had noticed a slowdown in gathering series images ... if you noticed too, you weren't imagining it.Re: 2017-06-07: Service disruption
Postby rkulagow » Thu Jun 22, 2017 10:09 am
An update at our upstream had a side-effect of causing their image formation queries to bypass cache and generate heavy loads during high traffic hours.
Nothing downloaded[6/26/2017 1:15:00 AM] ===============================================================================
[6/26/2017 1:15:00 AM] Beginning epg123 update execution.
[6/26/2017 1:15:00 AM] ===============================================================================
[6/26/2017 1:15:00 AM] [ INFO] Beginning EPG123 update execution. 2017-06-26 08:15:00Z
[6/26/2017 1:15:00 AM] [ INFO] DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: False , AutoAddNew: True
[6/26/2017 1:15:01 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[6/26/2017 1:15:01 AM] [ INFO] Status request successful. account expires: 2018-03-24T11:39:31Z , lineups: 1/4 , lastDataUpdate: 2017-06-25T21:49:44Z
[6/26/2017 1:15:01 AM] [ INFO] system status: Online , message: No known issues.
[6/26/2017 1:15:01 AM] [ INFO] epg123 is up to date. version: 1.1.8
[6/26/2017 1:15:01 AM] [ INFO] Successfully retrieved TMDb configurations.
[6/26/2017 1:15:01 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[6/26/2017 1:15:01 AM] Entering buildLineupServices() for 1 lineups.
[6/26/2017 1:15:01 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04768-X.
[6/26/2017 1:15:02 AM] Exiting buildLineupServices(). SUCCESS.
[6/26/2017 1:15:02 AM] Entering getAllScheduleEntryMd5s() for 30 days on 442 stations.
[6/26/2017 1:15:08 AM] [ INFO] Successfully retrieved Md5s for 442 station's daily schedules.
[6/26/2017 1:15:09 AM] [ INFO] Found 9030 cached daily schedules.
[6/26/2017 1:15:09 AM] [ INFO] Downloaded 0 daily schedules.
[6/26/2017 1:15:41 AM] [ INFO] Processed 9030 daily schedules for 442 stations.
[6/26/2017 1:15:41 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
Schedules Direct's servers were down for maintenance a few days ago ... at least that's what the server responded with. I do recall there being a banner on their webpage stating there were problems being worked.Sammy2 wrote:Sorry I never responded to this. All is well with the exception of a Schedules Direct Server down error last week. Don't remember which day it was as I was on vacation but I had clean runs for the last several runs and a full 21 days data right now.
Yea, RobertK was doing some scheduled maintenance.garyan2 wrote:Schedules Direct's servers were down for maintenance a few days ago ... at least that's what the server responded with. I do recall there being a banner on their webpage stating there were problems being worked.
That would explain why I got the bad gateway error last week. Does Schedules Direct post about these outages? I just looked on the SD forum and didn't see anything.rmeden wrote:Yea, RobertK was doing some scheduled maintenance.garyan2 wrote:Schedules Direct's servers were down for maintenance a few days ago ... at least that's what the server responded with. I do recall there being a banner on their webpage stating there were problems being worked.
Every 5 minutes I run a test against the SD-DD and SD-JSON services. If there is one failure it says "possibly down". If there are two, it updates the banner to say it's down.... Once it comes back it says recovering until it's been up for a while (duration depends on outage length). After a few cycles it also starts sending text messages to us asking for help.