Page 1 of 1

AMC Error

Posted: 19 Jun 2016, 16:52
by nekromantik
Hi all
I seem to get this error every now and again recently.
It happens once and then the next time amc is called it works fine.
Seems to happen once every day or two.
Is it problem on server side?

Code: Select all

@java.lang.IllegalStateException: Failed to retrieve authorization token: Read timed out
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Failed to retrieve authorization token: Read timed out
    at net.filebot.WebServices$TheTVDBClientWithLocalSearch.fetchSearchResult(WebServices.java:136)
    at net.filebot.web.AbstractEpisodeListProvider.lambda$search$0(AbstractEpisodeListProvider.java:22)
    at net.filebot.Cache.computeIf(Cache.java:85)
    at net.filebot.Cache$TypedCache.computeIf(Cache.java:166)
    at net.filebot.Cache.computeIfAbsent(Cache.java:91)
    at net.filebot.Cache$TypedCache.computeIfAbsent(Cache.java:171)
    at net.filebot.web.AbstractEpisodeListProvider.search(AbstractEpisodeListProvider.java:21)
    at net.filebot.cli.CmdlineOperations.fetchEpisodeSet(CmdlineOperations.java:288)
    at net.filebot.cli.CmdlineOperations.renameSeries(CmdlineOperations.java:207)
    at net.filebot.cli.CmdlineOperations.rename(CmdlineOperations.java:110)
    at net.filebot.cli.ScriptShellBaseClass.rename(ScriptShellBaseClass.java:336)
    at Script1$_run_closure72.doCall(Script1.groovy:371)
    at Script1.run(Script1.groovy:356)
    at net.filebot.cli.ScriptShell.evaluate(ScriptShell.java:62)
    at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:72)
    at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:114)
    at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:29)
    at net.filebot.Main.main(Main.java:117)
Caused by: java.lang.IllegalStateException: Failed to retrieve authorization token: Read timed out
    at net.filebot.web.TheTVDBClient.getAuthorizationToken(TheTVDBClient.java:96)
    at net.filebot.web.TheTVDBClient.getRequestHeader(TheTVDBClient.java:79)
    at net.filebot.web.TheTVDBClient.lambda$requestJson$0(TheTVDBClient.java:64)
    at net.filebot.CachedResource.lambda$fetchIfModified$8(CachedResource.java:186)
    at net.filebot.CachedResource.lambda$null$0(CachedResource.java:83)
    at net.filebot.CachedResource.retry(CachedResource.java:112)
    at net.filebot.CachedResource.lambda$get$1(CachedResource.java:83)
    at net.filebot.Cache.computeIf(Cache.java:85)
    at net.filebot.CachedResource.get(CachedResource.java:78)
    at net.filebot.web.TheTVDBClient.requestJson(TheTVDBClient.java:64)
    at net.filebot.web.TheTVDBClient.search(TheTVDBClient.java:104)
    at net.filebot.web.TheTVDBClient.fetchSearchResult(TheTVDBClient.java:123)
    at net.filebot.WebServices$TheTVDBClientWithLocalSearch.access$001(WebServices.java:111)
    at net.filebot.WebServices$TheTVDBClientWithLocalSearch.lambda$fetchSearchResult$3(WebServices.java:132)
Caused by: java.net.SocketTimeoutException: Read timed out
    at net.filebot.web.WebRequest.post(WebRequest.java:196)
    at net.filebot.web.TheTVDBClient.postJson(TheTVDBClient.java:58)
    at net.filebot.web.TheTVDBClient.getAuthorizationToken(TheTVDBClient.java:92)
    ... 13 more

Re: AMC Error

Posted: 19 Jun 2016, 17:13
by rednoah
Yep. Read timed out means that TheTVDB API service didn't respond to the auth request within 60 seconds. As the new API is new, making things run smoothly on the server-side might take a while.

Although there might not much they can do, if you really get a lot of server timeouts, it's probably worth posting about this issue in the TheTVDB forums.

Re: AMC Error

Posted: 19 Jun 2016, 18:24
by nekromantik
Ok
thanks

Re: AMC Error

Posted: 06 Jul 2016, 20:33
by nekromantik
I posted on tvdb forums and its been a week and no one responded.
:(
Keeps happening, half the files get the error every day.

Re: AMC Error

Posted: 07 Jul 2016, 04:49
by rednoah
Have you tried the latest revision? It's using the new TheTVDB API (which may or may not work better for you).

EDIT:

According to the logs you are using the latest revision. Try the last stable release instead. The old API might be more reliable.