Schedule Update Timeouts

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
Post Reply
glorp

Posts: 354
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

Schedule Update Timeouts

#1

Post by glorp » Sun Mar 06, 2016 3:51 pm

After about a weeks' worth of successful updates, todays' run failed like when I reported trouble before. I have the full trace, which is very short, and I'm adding below. The lineup ID was edited. This was a run from v0.7.3. It ran off my scheduled task and I just let it fail and run to completion. I haven't touched WMC or the GUI since. If anything else would be useful for debugging let me know. AFAIK, rkulagow enabled tracing on my SD account and it is still active. You have my permission to get or be sent whatever you might need from that account, or if you need me to get it, I will. rkulagow knows my account name (which is not "glorp"). I won't run another update attempt until tomorrow I think. New data isn't an issue for a while.

BTW: The last failed run was exactly 7 days ago at the same time of day. Users doing weekend updates @ SD causing high load, slower response maybe ?

Code: Select all

[3/6/2016 7:30:03 AM] Entering sdGetToken().
[3/6/2016 7:30:04 AM] Exiting sdGetToken(). SUCCESS.
[3/6/2016 7:30:04 AM] Entering sdCheckVersion().
[3/6/2016 7:30:04 AM] Exiting sdCheckVersion(). SUCCESS.
[3/6/2016 7:30:05 AM] Entering sdGetLineups().
[3/6/2016 7:30:05 AM] Exiting sdGetLineups(). SUCCESS.
[3/6/2016 7:30:05 AM] Entering sdGetStationsMaps() for lineup USA-XXXXXX-X.
[3/6/2016 7:30:05 AM] Exiting sdGetStationMaps(). SUCCESS.
[3/6/2016 7:30:06 AM] Entering buildAllScheduleEntries() for 520 stations and 14 days.
[3/6/2016 7:30:06 AM] Entering sdGetScheduleListings() for 520 daily schedules.
[3/6/2016 7:31:06 AM] WebException Thrown. Message: The operation has timed out, Status: Timeout
[3/6/2016 7:31:06 AM] Changing timeout to 120 seconds and trying again.
[3/6/2016 7:33:06 AM] WebException Thrown. Message: The operation has timed out, Status: Timeout
[3/6/2016 7:33:06 AM] Changing timeout to 180 seconds and trying again.
[3/6/2016 7:36:06 AM] WebException Thrown. Message: The operation has timed out, Status: Timeout
[3/6/2016 7:36:06 AM] Changing timeout to 240 seconds and trying again.
[3/6/2016 7:40:06 AM] WebException Thrown. Message: The operation has timed out, Status: Timeout
[3/6/2016 7:40:06 AM] Failed to complete request. Exiting
[3/6/2016 7:40:06 AM] Null response. Exiting sdGetScheduleListings().
[3/6/2016 7:40:06 AM] Problem occurred during buildScheduleEntries(). Exiting.
[3/6/2016 7:40:06 AM] Failed to create MXF file. Exiting.

User avatar
STC

Posts: 6808
Joined: Mon Jun 06, 2011 4:58 pm
Location:

HTPC Specs: Show details

#2

Post by STC » Sun Mar 06, 2016 4:08 pm

I get the initial 120s timeout quite often but it retries and always succeeds FWIW.
By the Community, for the Community. 100% Commercial Free.

Want decent guide data back? Check out EPG123

glorp

Posts: 354
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#3

Post by glorp » Sun Mar 06, 2016 4:21 pm

For the past week it's been binary for me. It either fails on timeouts or has none at all. I just double checked the last 7 days' traces.

HTBruceM

Posts: 87
Joined: Sat Dec 22, 2012 12:42 am
Location: Oregon

HTPC Specs: Show details

#4

Post by HTBruceM » Sun Mar 06, 2016 7:00 pm

No timeouts for me in the last several days, although I've seen it do the 120, 180 thing a few times.

Got this today (from the command window while it was running), which is new.. I haven't seen the tmdb requests delay before..

Code: Select all

Requesting Token from Schedules Direct ...
Retrieving list of subscribed lineups ...

Retrieving StationID / channel mapping for lineup (1/1) ...
Lineup 1 (Frontier Fios Portland - Digital) includes 546 stations.
Processing station 546/546

Requesting schedule entries for 21 days on 546 stations ...
Processing 11466/11466 daily station schedules

Retrieving 48929 programs from local cache and Schedules Direct ...
Processing program 44976/48929 ... tmdb requests delay for 4 seconds
Processing program 45011/48929 ... tmdb requests delay for 4 seconds
Processing program 45070/48929 ... tmdb requests delay for 4 seconds
Processing program 45177/48929 ... tmdb requests delay for 2 seconds
Processing program 45190/48929 ... tmdb requests delay for 5 seconds
Processing program 45203/48929 ... tmdb requests delay for 4 seconds
Processing program 45217/48929 ... tmdb requests delay for 4 seconds
Processing program 45230/48929 ... tmdb requests delay for 4 seconds
Processing program 45243/48929 ... tmdb requests delay for 4 seconds
Processing program 47008/48929 ... tmdb requests delay for 2 seconds
Processing program 47033/48929 ... tmdb requests delay for 2 seconds
Processing program 47058/48929 ... tmdb requests delay for 2 seconds
Processing program 47080/48929 ... tmdb requests delay for 3 seconds
Processing program 47104/48929 ... tmdb requests delay for 2 seconds
Processing program 47134/48929 ... tmdb requests delay for 1 seconds
Processing program 47156/48929 ... tmdb requests delay for 3 seconds
Processing program 47182/48929 ... tmdb requests delay for 2 seconds
Processing program 47210/48929 ... tmdb requests delay for 2 seconds
Processing program 47231/48929 ... tmdb requests delay for 3 seconds
Processing program 47263/48929 ... tmdb requests delay for 1 seconds
Processing program 47288/48929 ... tmdb requests delay for 2 seconds
Processing program 47322/48929 ... tmdb requests delay for 1 seconds
Processing program 47349/48929 ... tmdb requests delay for 2 seconds
Processing program 47379/48929 ... tmdb requests delay for 1 seconds
Processing program 47400/48929 ... tmdb requests delay for 3 seconds
Processing program 47427/48929 ... tmdb requests delay for 2 seconds
Processing program 47442/48929 ... tmdb requests delay for 4 seconds
Processing program 47456/48929 ... tmdb requests delay for 4 seconds
Processing program 47469/48929 ... tmdb requests delay for 4 seconds
Processing program 47511/48929 ... tmdb requests delay for 4 seconds
Processing program 48622/48929 ... tmdb requests delay for 1 seconds
Processing program 48650/48929 ... tmdb requests delay for 3 seconds
Processing program 48765/48929 ... tmdb requests delay for 3 seconds
Processing program 48929/48929

Retrieving image links for 8190 series ...
Processing images for series 8190/8190

Importing guide data into Windows Media Center ...

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Mon Mar 07, 2016 5:47 am

HTBruceM wrote:No timeouts for me in the last several days, although I've seen it do the 120, 180 thing a few times.

Got this today (from the command window while it was running), which is new.. I haven't seen the tmdb requests delay before..

Code: Select all

Requesting Token from Schedules Direct ...
Retrieving list of subscribed lineups ...

Retrieving StationID / channel mapping for lineup (1/1) ...
Lineup 1 (Frontier Fios Portland - Digital) includes 546 stations.
Processing station 546/546

Requesting schedule entries for 21 days on 546 stations ...
Processing 11466/11466 daily station schedules

Retrieving 48929 programs from local cache and Schedules Direct ...
Processing program 44976/48929 ... tmdb requests delay for 4 seconds
Processing program 45011/48929 ... tmdb requests delay for 4 seconds
Processing program 45070/48929 ... tmdb requests delay for 4 seconds
Processing program 45177/48929 ... tmdb requests delay for 2 seconds
Processing program 45190/48929 ... tmdb requests delay for 5 seconds
Processing program 45203/48929 ... tmdb requests delay for 4 seconds
Processing program 45217/48929 ... tmdb requests delay for 4 seconds
Processing program 45230/48929 ... tmdb requests delay for 4 seconds
Processing program 45243/48929 ... tmdb requests delay for 4 seconds
Processing program 47008/48929 ... tmdb requests delay for 2 seconds
Processing program 47033/48929 ... tmdb requests delay for 2 seconds
Processing program 47058/48929 ... tmdb requests delay for 2 seconds
Processing program 47080/48929 ... tmdb requests delay for 3 seconds
Processing program 47104/48929 ... tmdb requests delay for 2 seconds
Processing program 47134/48929 ... tmdb requests delay for 1 seconds
Processing program 47156/48929 ... tmdb requests delay for 3 seconds
Processing program 47182/48929 ... tmdb requests delay for 2 seconds
Processing program 47210/48929 ... tmdb requests delay for 2 seconds
Processing program 47231/48929 ... tmdb requests delay for 3 seconds
Processing program 47263/48929 ... tmdb requests delay for 1 seconds
Processing program 47288/48929 ... tmdb requests delay for 2 seconds
Processing program 47322/48929 ... tmdb requests delay for 1 seconds
Processing program 47349/48929 ... tmdb requests delay for 2 seconds
Processing program 47379/48929 ... tmdb requests delay for 1 seconds
Processing program 47400/48929 ... tmdb requests delay for 3 seconds
Processing program 47427/48929 ... tmdb requests delay for 2 seconds
Processing program 47442/48929 ... tmdb requests delay for 4 seconds
Processing program 47456/48929 ... tmdb requests delay for 4 seconds
Processing program 47469/48929 ... tmdb requests delay for 4 seconds
Processing program 47511/48929 ... tmdb requests delay for 4 seconds
Processing program 48622/48929 ... tmdb requests delay for 1 seconds
Processing program 48650/48929 ... tmdb requests delay for 3 seconds
Processing program 48765/48929 ... tmdb requests delay for 3 seconds
Processing program 48929/48929

Retrieving image links for 8190 series ...
Processing images for series 8190/8190

Importing guide data into Windows Media Center ...
TMDb limits API requests to 40 in a 10 second window IIRC ... the server will respond with a time required to wait before it will accept the next request. When you see these bunched together like that, than you are probably scanning through a movie channel that SD doesn't have any images for. More than likely a foreign channel.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Mon Mar 07, 2016 5:54 am

I hadn't realized the potential for so many timeouts on the server out there. I've seen a timeout once, maybe twice. The likelyhood of this will be lessened when I get the daily schedules cached as well as programs which I am hoping will be real soon. In the interim, I think I'll change the base timeout from 60 seconds to 120 seconds. Then the progression will be 120, 240, 360, 480 seconds. Just seems like an awful long time.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Mon Mar 07, 2016 6:44 am

Just posted the new version (v0.7.5) with the doubled timeouts. Also has much better tracing. http://epg123.garyan2.net
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

Post Reply