[ERROR] SD API WebException Thrown.

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

[ERROR] SD API WebException Thrown.

Post#1 » Wed Oct 11, 2017 12:29 pm

Yesterday's run:

Code: Select all
[10/10/2017 1:15:00 AM] ===============================================================================
[10/10/2017 1:15:00 AM]  Beginning epg123 update execution.
[10/10/2017 1:15:00 AM] ===============================================================================
[10/10/2017 1:15:00 AM] [ INFO] Beginning EPG123 update execution. 2017-10-10 08:15:00Z
[10/10/2017 1:15:00 AM] [ INFO] DaysToDownload: 21 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[10/10/2017 1:15:01 AM] [ INFO] Token request successful. serverID: 20141201.web.2
[10/10/2017 1:15:01 AM] [ INFO] Status request successful. account expires: 2018-03-24T11:39:31Z , lineups: 1/4 , lastDataUpdate: 2017-10-10T06:15:56Z
[10/10/2017 1:15:01 AM] [ INFO] system status: Online , message: No known issues.
[10/10/2017 1:15:01 AM] [ INFO] epg123 is up to date. version: 1.1.17
[10/10/2017 1:15:01 AM] [ INFO] Successfully retrieved TMDb configurations.
[10/10/2017 1:15:02 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[10/10/2017 1:15:02 AM] Entering buildLineupServices() for 1 lineups.
[10/10/2017 1:15:02 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04768-X.
[10/10/2017 1:15:03 AM] Exiting buildLineupServices(). SUCCESS.
[10/10/2017 1:15:03 AM] Entering getAllScheduleEntryMd5s() for 21 days on 436 stations.
[10/10/2017 1:15:07 AM] [ INFO] Successfully retrieved Md5s for 436 station's daily schedules.
[10/10/2017 1:15:09 AM] [ INFO] Found 5409 cached daily schedules.
[10/10/2017 1:15:12 AM] [ INFO] Successfully retrieved 436 station's daily schedules.
[10/10/2017 1:15:32 AM] [ INFO] Downloaded 3732 daily schedules.
[10/10/2017 1:15:53 AM] [ INFO] Processed 9141 daily schedules for 436 stations.
[10/10/2017 1:15:53 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[10/10/2017 1:15:53 AM] Entering buildAllProgramEntries() for 46137 programs.
[10/10/2017 1:17:41 AM] [ INFO] Found 36609 cached program descriptions.
[10/10/2017 1:19:41 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[10/10/2017 1:19:41 AM] [ INFO] Changing timeout to 240 seconds and trying again.
[10/10/2017 1:23:41 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[10/10/2017 1:23:41 AM] [ INFO] Changing timeout to 360 seconds and trying again.
[10/10/2017 1:28:42 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (504) Gateway Timeout. , Status: ProtocolError
[10/10/2017 1:28:43 AM] [ERROR] Did not receive a response from Schedules Direct for 5000 program descriptions.
[10/10/2017 1:28:43 AM] Problem occurred during buildProgramEntries(). Exiting.
[10/10/2017 1:28:43 AM] [ERROR] Failed to create MXF file. Exiting.
[10/10/2017 1:28:43 AM] [ INFO] epg123 update execution time was 00:13:42.7220570.
[10/10/2017 1:28:43 AM] ===============================================================================
[10/10/2017 1:28:43 AM]  Beginning epg123 client execution.
[10/10/2017 1:28:43 AM] ===============================================================================
[10/10/2017 1:28:43 AM] [ INFO] Beginning epg123 client execution. 2017-10-10 08:28:43Z
[10/10/2017 1:28:43 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False
[10/10/2017 1:28:43 AM] [ INFO] epg123 client version: 1.1.17 for Win7
[10/10/2017 1:28:43 AM] Entering importMxfFile() for file "C:\epg123\epg123.mxf"
[10/10/2017 1:30:22 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[10/10/2017 1:30:22 AM] Exiting importMxfFile(). SUCCESS.
[10/10/2017 1:30:23 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[10/10/2017 1:30:23 AM] Entering reindexDatabase()
[10/10/2017 1:30:23 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[10/10/2017 1:30:23 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[10/10/2017 1:30:23 AM] Exiting reindexDatabase(). SUCCESS.
[10/10/2017 1:30:23 AM] [ INFO] Completed EPG123 client execution.
[10/10/2017 1:30:23 AM] [ INFO] EPG123 client execution time was 00:01:40.6287556.


Today's was fine. Issues with Schedules Direct Servers early morning 10/10/2017?
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#2 » Wed Oct 11, 2017 1:56 pm

We've started adding TheTVDB metadata to programs, which changes the MD5, which means that lots of clients were refreshing their local caches. We added servers to the pool to service the increased traffic.
rkulagow
 
Posts: 225
Joined: 19 July 2015
Location: Schedules Direct

Post#3 » Wed Oct 11, 2017 2:13 pm

rkulagow wrote:We've started adding TheTVDB metadata to programs, which changes the MD5, which means that lots of clients were refreshing their local caches. We added servers to the pool to service the increased traffic.
As always you guys are on top of it!

Does this mean even MORE information beyond what Gracenote provides?

Thanks!

Sent from my SM-G930P using Tapatalk
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#4 » Wed Oct 11, 2017 3:12 pm

It's in the raw data; it's up to EPG123 to parse and use it.
rkulagow
 
Posts: 225
Joined: 19 July 2015
Location: Schedules Direct

Post#5 » Wed Oct 11, 2017 3:44 pm

The only thing EPG123 uses right now is the season and episode numbers from TheTVDB provided by SD. It is optional since v1.1.16. The other information provided by SD is the series ID and episode ID of the program so if in the future we want to get additional information from TVDB, we can.

Just a note since it was brought up ... since I released this ability in EPG123, I have found a "bug" in that WMC limits the season number to 255. There are some series in TVDB that list their season as the year of production, so season 1971 for a season that was broadcast in 1971. For all those seasons that do this, WMC clips it to season 255. What that means is EPG123/WMC will have every season for the series as 255 which can seriously confuse people. I haven't decided whether I will just ignore the TVDB S/E numbers in this case, or simply use the last 2 digits for a season number. Whichever I decide, it will be in the next release.
User avatar
garyan2
 
Posts: 2200
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 » Wed Oct 11, 2017 9:07 pm

I got the SD timeout errors for the last 2 days... hopefully the server scaleup helps.
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#7 » Thu Oct 12, 2017 5:36 am

garyan2 wrote:The only thing EPG123 uses right now is the season and episode numbers from TheTVDB provided by SD. It is optional since v1.1.16. The other information provided by SD is the series ID and episode ID of the program so if in the future we want to get additional information from TVDB, we can.

Just a note since it was brought up ... since I released this ability in EPG123, I have found a "bug" in that WMC limits the season number to 255. There are some series in TVDB that list their season as the year of production, so season 1971 for a season that was broadcast in 1971. For all those seasons that do this, WMC clips it to season 255. What that means is EPG123/WMC will have every season for the series as 255 which can seriously confuse people. I haven't decided whether I will just ignore the TVDB S/E numbers in this case, or simply use the last 2 digits for a season number. Whichever I decide, it will be in the next release.

One other option is to use <season number> - <series start year> + 1

So if the series started in 1980, and the season number is 1980, the resulting season in WMC would be "1". Of course the series start year would have to be known and correct for it to work, and it might be more trouble than it is worth...
Space
 
Posts: 1165
Joined: 2 June 2013

Post#8 » Thu Oct 12, 2017 6:10 am

Space wrote:One other option is to use <season number> - <series start year> + 1

That’s a good suggestion if possible.

One UK example of this is Horizon which started in 1964. So not long until we reach 64 again. ;)
https://www.thetvdb.com/?tab=series&id=74379

What does the Gracenote data give in these cases?
User avatar
IT Troll
 
Posts: 496
Joined: 27 November 2011
Location: Edinburgh, UK
HTPC Specs: Show details
5+ YrsTGB Veteran

Post#9 » Thu Oct 12, 2017 1:59 pm

Another day wihout data download, same timeouts. Doesn't look like the extra servers at SD helped me at least, down to 13 days expecting 16:

Code: Select all
[10/12/2017 2:01:00 AM] [ INFO] Beginning EPG123 update execution. 2017-10-12 08:01:00Z
[10/12/2017 2:01:00 AM] [ INFO] DaysToDownload: 16 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: False , AutoAddNew: True
[10/12/2017 2:01:01 AM] [ INFO] Token request successful. serverID: 20141201.web.2
[10/12/2017 2:01:01 AM] [ INFO] Status request successful. account expires: 2018-04-23T01:40:15Z , lineups: 1/4 , lastDataUpdate: 2017-10-12T01:26:46Z
[10/12/2017 2:01:01 AM] [ INFO] system status: Online , message: No known issues.
[10/12/2017 2:01:01 AM] [WARNG] epg123 is not up to date. Latest version is 1.1.17 and can be downloaded from http://epg123.garyan2.net.
[10/12/2017 2:01:01 AM] [ INFO] Successfully retrieved TMDb configurations.
[10/12/2017 2:01:02 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[10/12/2017 2:01:02 AM] Entering buildLineupServices() for 1 lineups.
[10/12/2017 2:01:02 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CO05459-X.
[10/12/2017 2:01:02 AM] Exiting buildLineupServices(). SUCCESS.
[10/12/2017 2:01:02 AM] Entering getAllScheduleEntryMd5s() for 16 days on 490 stations.
[10/12/2017 2:01:46 AM] [ INFO] Successfully retrieved Md5s for 490 station's daily schedules.
[10/12/2017 2:01:47 AM] [ INFO] Found 5458 cached daily schedules.
[10/12/2017 2:01:55 AM] [ INFO] Successfully retrieved 490 station's daily schedules.
[10/12/2017 2:02:01 AM] [ INFO] Downloaded 2382 daily schedules.
[10/12/2017 2:02:09 AM] [ INFO] Processed 7840 daily schedules for 490 stations.
[10/12/2017 2:02:09 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[10/12/2017 2:02:09 AM] Entering buildAllProgramEntries() for 43482 programs.
[10/12/2017 2:02:31 AM] [ INFO] Found 30488 cached program descriptions.
[10/12/2017 2:04:32 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[10/12/2017 2:04:32 AM] [ INFO] Changing timeout to 240 seconds and trying again.
[10/12/2017 2:08:32 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
[10/12/2017 2:08:32 AM] [ INFO] Changing timeout to 360 seconds and trying again.
[10/12/2017 2:13:32 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (504) Gateway Timeout. , Status: ProtocolError
[10/12/2017 2:13:32 AM] [ERROR] Did not receive a response from Schedules Direct for 5000 program descriptions.
[10/12/2017 2:13:32 AM] Problem occurred during buildProgramEntries(). Exiting.
[10/12/2017 2:13:32 AM] [ERROR] Failed to create MXF file. Exiting.
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#10 » Thu Oct 12, 2017 2:56 pm

Please open a ticket at the Schedules Direct website. I just checked the servers in the pool, and they're not experiencing heavy load right now that would cause your system to timeout.
rkulagow
 
Posts: 225
Joined: 19 July 2015
Location: Schedules Direct

Post#11 » Thu Oct 12, 2017 8:22 pm

All right, a ticket has been opened. Thanks.
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#12 » Thu Oct 12, 2017 11:33 pm

Bummer. I didn't check mine today. Guess I better take a look.
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#13 » Fri Oct 13, 2017 12:26 am

You guys could manually initiate an update... updating at an odd time would probably mean a higher probability of success. It would also mean less programs to cache/update due to the new MD5 hash.
User avatar
garyan2
 
Posts: 2200
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#14 » Fri Oct 13, 2017 12:45 am

My run last night and the night before went fine although the run time was a bit longer than usually. Nearly 20 minutes on 10/10 and about 15 minutes last night. Is this to be expected?
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#15 » Fri Oct 13, 2017 1:18 am

Sammy2 wrote:Bummer. I didn't check mine today. Guess I better take a look.


You know you can set up to get an e-mail or text when EPG123 fails so you never have to check.
See this post: http://www.thegreenbutton.tv/forums/viewtopic.php?f=99&t=10984
stuartm
 
Posts: 327
Joined: 5 November 2012
Location: Longmont, CO
HTPC Specs: Show details

Post#16 » Fri Oct 13, 2017 4:38 pm

stuartm wrote:
Sammy2 wrote:Bummer. I didn't check mine today. Guess I better take a look.


You know you can set up to get an e-mail or text when EPG123 fails so you never have to check.
See this post: http://www.thegreenbutton.tv/forums/viewtopic.php?f=99&t=10984


You know, I saw that discussion back then but put it in the back of my mind. Thanks for bringing it to the forefront again. I'll give it a try.
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details

Post#17 » Fri Oct 13, 2017 7:56 pm

Failed again for me last night, about 4th night in a row. Sent logs to SD.
webminster
 
Posts: 652
Joined: 20 December 2011
HTPC Specs: Show details
-Alan

Post#18 » Mon Oct 16, 2017 2:05 pm

Other than a couple of Time Discontinuity Errors I'm getting data still.
Sammy2
 
Posts: 1352
Joined: 24 August 2012
HTPC Specs: Show details


Return to EPG123



Who is online

Users browsing this forum: No registered users and 3 guests

cron