Slow Updates: 20170829

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

Slow Updates: 20170829

Post#1 » Wed Aug 30, 2017 1:51 am

Everyone...

It looks like the TMDB API is having issues right now and is causing EPG123 to pretty much hang at the beginning of an update. The API continually advises to wait 9-10 seconds to try again and my code has no mechanism to jump out of the loop. The API does eventually respond, but who knows how long it will take.

From their website/forum:
Reply by Travis Bell on August 29, 2017 at 2:43PM
Confirmed, we're having trouble keeping up with price fluctuations in the AWS spot market. I'll let update this thread once it looks like things have settled back down to normal.

Update @ 4:49PM MST: We're still working on it.

But he says everything is back up ... maybe just overloaded at the moment.
Reply by Travis Bell on August 29, 2017 at 6:31PM
Everything has returned back to normal. Sorry about that guys.

I'll keep an eye on it and the next release will have a mechanism to skip TMDB access if it appears they are having problems.
User avatar
garyan2
 
Posts: 2152
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#2 » Wed Aug 30, 2017 5:00 am

This is waaaay over my head, but some of you uber geeks probably think it's old hat.

Reply by Travis Bell on August 29, 2017 at 9:50PM
Ya, so what's happening is either Nginx or ELB (I'm not entirely sure which) is creating pseudo ipv4 addresses created within the protected 10.x IP namespace. There's a little bit about this online but it's hard to get much information about. What's happening with these "fake" IP addresses is that a lot of you are sharing an IP address. I bet if you reload that debug URL, you might even get a different IP at different times.

I admit to not fully testing this because everything worked properly on the website but there's an important difference that I didn't think of which is CloudFront. We use CloudFront on the website and not the API.

I'm going to revert today's ipv6 change and disable it again on the API until this gets figured out. It might be another few hours before ipv6 is disabled properly on api.themoviedb.org.

You can try to use api.tmdb.org and see if it makes any difference but I suspect it won't. It's something you can try.
User avatar
garyan2
 
Posts: 2152
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#3 » Wed Aug 30, 2017 5:24 am

Okay, IPv6 has been disabled on the TMDB servers and service has been restored.
User avatar
garyan2
 
Posts: 2152
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net


Return to EPG123



Who is online

Users browsing this forum: No registered users and 2 guests

cron