Error: `acd_cli` handling of expired `oauth_token` (refreshing) about acd_cli

[chrisidefix]

UPDATE: after uploading about 100 GB I am receiving the same error again within a few hours of having this problem initially. Any idea what might be going on here? Is it possible that Amazon is resetting the oauth_token or what could this be related to?

PS: after deleting the cache (again) and downloading a new oauth_token I can continue to upload

[yadayada]

The next time this happens, please check that the oauth_data file in your cache directory is correct.

Aside from this, this is basically the indended behavior when the access token cannot be refreshed. There is nothing I can do about a connection error.

But I will wrap the connection error so the exception can be caught and the upload/download queue can potentially process further jobs (and retry the token refresh).

[chrisidefix]

How do I check if oauth_data is correct? It's been in the cache directory since I started using acd_cli and I never changed it. For now I have to keep replacing it every couple of hours. Do you know from the error if the connection error happens with an amazon domain or with https://tensile-runway-92512.appspot.com ? I would like to figure out what is going on if possible.

[yadayada]

You will simply see if there is something wrong. It needs to be refreshed every hour.
It should look something like the below block basically, with one additional field and longer tokens.

{
    "token_type": "bearer",
    "expires_in": 3600,
    "refresh_token": "Atzr|IQEBLzAtAhUAibmh-1N0EVztZJofMx",
    "access_token": "Atza|IQEBLjAsAhQ3yD47Jkj09BfU_qgNk4"
}

The connection error tells me nothing. There should always be a response from the appspot server, even an empty response on error.
I also had a quick look at the server logs and didn't find any failed requests, purely judging from the response length.

Maybe it's a threading error.

[chrisidefix]

My oauth_data looks like you describe it and fine from what I can see (it has exp_time: set as well)

Maybe it's a threading error.

Possibly, but this is not (only) happening when running multiple threads. I actually first saw this error on calling acd_cli.py s (after not using acd_cli.py for a day or two, I wanted to sync again).

Now, this is a repetitive problem for me. Uploading works for a while, but as soon as this error has occurred once (usually while uploading), all I can do is replace oauth_data and restart the uploads. I don't understand why a new oauth_data fixes this, but it does.

Or does this mean that right now I can not refresh the token at all and it probably only works for 3600 seconds, because it doesn't need to refresh during the first hour after generation of oauth_data?

[chrisidefix]

During upload (with `acd_cli.py -x 8) I get this error:

15-05-21 19:04:37.065 [ERROR] [acdcli.api.oauth] - Error refreshing authentication token.
15-05-21 19:04:37.066 [ERROR] [acd_cli] - Uploading "test_file.txt" failed. Code: 1000, msg: ('Connection aborted.', OSError(64, 'Host is down'))

Even if I try uploading with a single thread or syncing after this happens, it just doesn't work.

[yadayada]

How should it work? Nothing can work with an outdated access token that cannot be refreshed.

Maybe it's a threading error.

Possibly,

Nope. If the data is intact, that shouldn't be it.

What does

python3 -c 'import requests; r = requests.post("https://tensile-runway-92512.appspot.com"); print(r.text, r.status_code)'

output?

The debug option could also shed more light on the connection error.

[chrisidefix]

Thanks for looking into this. The above command seems to produce the same error. I assume it must be a problem on my side in this case. Maybe my firewall is acting up - I am going to re-install it and see if that helps anything.

[chrisidefix]

Alright, I managed to re-install my firewall, which appeared to have blocked connections to the appspot.com address and crashed it's UI at the same time, so I didn't receive any info about this.

You are welcome to close this issue. Thanks for your help!