Schedules Direct Broke?

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
eclas

Posts: 151
Joined: Wed Feb 25, 2015 2:38 am
Location:

HTPC Specs: Show details

Schedules Direct Broke?

#1

Post by eclas » Sat May 21, 2022 10:27 am

Anyone else getting a token error when trying to update their guide?
I'm getting the error on 2 different systems.

sjr56stn

Posts: 77
Joined: Tue Mar 03, 2015 4:49 pm
Location:

HTPC Specs: Show details

#2

Post by sjr56stn » Sat May 21, 2022 10:46 am

Yes, I am getting the same problem when I tried a manual EPG123 update. My overnight update worked OK. I manually logged on to SD this morning with no problems, but the issuing of tokens to EPG123 seems to be broken.

User avatar
alhaunts

Posts: 66
Joined: Wed Jan 01, 2020 5:45 pm
Location:

HTPC Specs: Show details

#3

Post by alhaunts » Sat May 21, 2022 11:30 am

Yep, same here.

eclas

Posts: 151
Joined: Wed Feb 25, 2015 2:38 am
Location:

HTPC Specs: Show details

#4

Post by eclas » Sat May 21, 2022 11:52 am

I'm sure Gary or Sched direct will correct it soon.

adsmgreen

Posts: 1
Joined: Sat May 21, 2022 12:03 pm
Location:

HTPC Specs: Show details

#5

Post by adsmgreen » Sat May 21, 2022 12:11 pm

Error reads :

Login failed:
Did not receive a response from Schedules Direct for a token request.

Newbie here. Thank you for a great community!

JohnF

Posts: 9
Joined: Sat Jul 08, 2017 7:10 pm
Location:

HTPC Specs: Show details

#6

Post by JohnF » Sat May 21, 2022 1:27 pm

Same here...

[5/21/2022 8:17:30 AM] [ INFO] SD API WebException Thrown. Message: The underlying connection was closed: An unexpected error occurred on a send. , Status: SendFailure
[5/21/2022 8:17:30 AM] [ INFO] Failed to complete request. Exiting
[5/21/2022 8:17:30 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[5/21/2022 8:17:30 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.

JohnF

Posts: 9
Joined: Sat Jul 08, 2017 7:10 pm
Location:

HTPC Specs: Show details

#7

Post by JohnF » Sat May 21, 2022 1:37 pm

Note SchedulesDirect Update occurred this morning during my 1st failure:

Notice: JSON service migration from PHP to Python
https://forums.schedulesdirect.org/view ... =18&t=3201

It is continuing to fail ever since this update

mafaldatv

Posts: 104
Joined: Tue Jun 14, 2016 11:44 pm
Location:

HTPC Specs: Show details

#8

Post by mafaldatv » Sat May 21, 2022 2:14 pm

Same here. Very early this morning and again 4 hours later (manual attempt)

After token failure, EPG123 then imported previous day's mxf file (successfully), reporting it is 24 hours old in log file.

BTW, you can test this without trying a download. Opening EPG123 Configuration Tool will report "Did not receive a response from Schedules Direct for a token request"
Last edited by mafaldatv on Sat May 21, 2022 2:31 pm, edited 1 time in total.

hotwirez

Posts: 1
Joined: Sat May 21, 2022 2:09 pm
Location:

HTPC Specs: Show details

#9

Post by hotwirez » Sat May 21, 2022 2:22 pm

I wanted to mention I'm seeing the same thing. I messed with it enough that I eventually got a 'Service Unavailable' message. But leading up to that it was the same error you guys mentioned. I should've looked around a bit more, I guess. This was a horrible day for me to choose to finally replace bad memory in my media center box and need to reset PlayReady, etc... Oh well. I'll leave it alone and check back here later.

Thanks for a great tool, Gary. Honestly, this one tool is what's been keeping WMC viable for me since the guide data went away. :)

bigal

Posts: 44
Joined: Sat May 21, 2022 2:31 pm
Location:

HTPC Specs: Show details

#10

Post by bigal » Sat May 21, 2022 2:39 pm

Same here.

bsyd

Posts: 9
Joined: Tue Mar 18, 2014 4:15 pm
Location:

HTPC Specs: Show details

#11

Post by bsyd » Sat May 21, 2022 3:44 pm

mafaldatv wrote: Sat May 21, 2022 2:14 pm Same here. Very early this morning and again 4 hours later (manual attempt)

After token failure, EPG123 then imported previous day's mxf file (successfully), reporting it is 24 hours old in log file.

BTW, you can test this without trying a download. Opening EPG123 Configuration Tool will report "Did not receive a response from Schedules Direct for a token request"
I am receiving the same error. Tried several times today.

Checked Schedules Direct forum and found this information. Looks like they made a change yesterday:
https://forums.schedulesdirect.org/view ... 535#p10535

Notice: JSON service migration from PHP to Python
Post by rkulagow » Fri May 20, 2022 9:04 am

Schedules Direct will be migrating our API20141201 backend service from PHP to Python starting on 2022-05-20. This is not a migration to API20191021, which is still under development.

----------------------------

Status:
2022-05-21T03:00:00Z - migration started.
2022-05-21T04:55:00Z - migration ended.

----------------------------

What should you expect?
The Python provided API has been created to be protocol compatible, so it's likely that you won't need to do anything if your grabber has implemented the published API.
The new service is provided by AWS API Gateway, so the issues you may have experienced if you were updating your schedule at your local midnight time should now be addressed.
The methods used to generate data on our backend servers have been updated, and there are a number of fields in the new JSON which will cause the MD5 values to change, so your application will refresh its local data. This is known as a cache invalidation - expect that there will be a large amount of data downloaded.
What changes will you see?
The schedules on the backend will be refreshed more often; we have migrated to a new data delivery mechanism from our upstream provider.
You should see 14 to 18 days of schedule data.
Images will be updated more often.
Lineup updates will be occur more often.
Schedules Direct will send lineup deletion notifications to your registered email address 30 days before a lineup is deleted, in order to give you time to migrate. Lineups are deleted by upstream providers if they're consolidating headends, or ending an offering - this typically occurs if a provider is migrating from analog (usually, the -DEFAULT lineup) to digital-only (-X)
What should you do if you have issues after the migration?
Check to see if you're running the latest version of your application / grabber. Developers were provided early access to the new delivery mechanism, and a number of issues were resolved.
Check the support forum for your application and engage the developer; they'll be the ones that can help you troubleshoot the application and the migration.
If you're still stuck, your developer will tell you to open a ticket with Schedules Direct. Please open a lineup support ticket on the SchedulesDirect webpage https://www.schedulesdirect.org/lineupsupport and indicate that you're having an issue, and that the developer of your application has directed you to open a ticket.

User avatar
Bee_Dee_3_Dee

Posts: 281
Joined: Tue Feb 19, 2013 4:39 pm
Location:

HTPC Specs: Show details

#12

Post by Bee_Dee_3_Dee » Sat May 21, 2022 4:32 pm

bigal wrote: Sat May 21, 2022 2:39 pmSame here.

me 2.

DSperber

Posts: 359
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#13

Post by DSperber » Sat May 21, 2022 5:21 pm

And of course me too.

Oy vey.

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#14

Post by garyan2 » Sat May 21, 2022 6:04 pm

All,

The SD service is running very slow, specifically the token server. EPG123 has a 3 second timeout on token requests, but my last attempt took 6 seconds to complete. I can of course release an update to extend the timeout period, but will wait on feedback from SD to see what the plans are on their end. For now, just know that the SD service is working but EPG123 is not patient enough right now in the current state of affairs.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

cbarbie

Posts: 25
Joined: Thu Mar 10, 2016 11:42 am
Location:

HTPC Specs: Show details

#15

Post by cbarbie » Sat May 21, 2022 6:27 pm

I can wait for 24-48 hours to see if SD service times get better. If not the timeout modification to EPG123 would be appreciated. :)

NWIU2B

Posts: 15
Joined: Mon Jul 03, 2017 8:28 pm
Location:

HTPC Specs: Show details

#16

Post by NWIU2B » Sat May 21, 2022 6:53 pm

Gosh. Three seconds seems like an extremely short timeout period generally. Is there some way in which the update process would be terribly bogged down by allowing perhaps a ten second timeout normally?

User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

#17

Post by garyan2 » Sat May 21, 2022 7:03 pm

You may think that now that it is an issue, but before the changeover we would get a response within a couple hundred milliseconds. The timeout for the token was set to 3 seconds primarily to keep the GUI from being unresponsive for too long and give feedback to the user that there an issue logging in; otherwise they will force a close on the GUI thinking it was locked up/crashed.

All other requests have a 5 minute timeout period.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

bigal

Posts: 44
Joined: Sat May 21, 2022 2:31 pm
Location:

HTPC Specs: Show details

#18

Post by bigal » Sat May 21, 2022 7:41 pm

The SD service is running very slow
I'm guessing that "SD" is Schedules Direct; if so, logging into that site, I couldn't find any heads up or announcement re problems......
.

cbarbie

Posts: 25
Joined: Thu Mar 10, 2016 11:42 am
Location:

HTPC Specs: Show details

#19

Post by cbarbie » Sat May 21, 2022 7:49 pm


RarbS

Posts: 1
Joined: Mon Nov 02, 2020 12:17 pm
Location:

HTPC Specs: Show details

#20

Post by RarbS » Sat May 21, 2022 8:02 pm

cbarbie wrote: Sat May 21, 2022 6:27 pm I can wait for 24-48 hours to see if SD service times get better. If not the timeout modification to EPG123 would be appreciated. :)
Same here 8-)
And thanks for all your work Gary!

Post Reply