首先,如果这是一个太愚蠢的问题,我很抱歉...这是我第一次尝试使用此脚本中涉及的任何技术(Python,驱动器api,oauth 2.0,等等)。我发誓,在发布问题之前,我一直在寻找和试用这个约一个星期。呵呵呵
我正在尝试使用google-api-python-client上传一个仅在终端上的Linux Debian上的大文件(3.5GiB)。我上传小文件时取得了一些成功,但是当我尝试上传大文件时,上传会在HTTP 401错误(未授权)启动后大约1~2小时停止。我一直在研究如何获得新的访问令牌,但收效甚微。
到目前为止,这是我的(更新的)代码:
#!/usr/bin/python
import httplib2
import pprint
import time
from apiclient.discovery import build
from apiclient.http import MediaFileUpload
from apiclient import errors
from oauth2client.client import OAuth2WebServerFlow
# Copy your credentials from the APIs Console
CLIENT_ID = 'myclientid'
CLIENT_SECRET = 'myclientsecret'
# Check https://developers.google.com/drive/scopes for all available scopes
OAUTH_SCOPE = 'https://www.googleapis.com/auth/drive'
# Redirect URI for installed apps
REDIRECT_URI = 'urn:ietf:wg:oauth:2.0:oob'
# Run through the OAuth flow and retrieve credentials
flow = OAuth2WebServerFlow(CLIENT_ID, CLIENT_SECRET, OAUTH_SCOPE, REDIRECT_URI)
authorize_url = flow.step1_get_authorize_url()
print 'Go to the following link in your browser: ' + authorize_url
code = raw_input('Enter verification code: ').strip()
credentials = flow.step2_exchange(code)
# Create an httplib2.Http object and authorize it with our credentials
http = httplib2.Http()
http = credentials.authorize(http)
drive_service = build('drive', 'v2', http=http)
# Insert a file
media_body = MediaFileUpload('bigfile.zip', mimetype='application/octet-stream', chunksize=1024*256, resumable=True)
body = {
'title': 'bigfile.zip',
'description': 'Big File',
'mimeType': 'application/octet-stream'
}
retries = 0
request = drive_service.files().insert(body=body, media_body=media_body)
response = None
while response is None:
try:
print http.request.credentials.access_token
status, response = request.next_chunk()
if status:
print "Uploaded %.2f%%" % (status.progress() * 100)
retries = 0
except errors.HttpError, e:
if e.resp.status == 404:
print "Error 404! Aborting."
exit()
else:
if retries > 10:
print "Retries limit exceeded! Aborting."
exit()
else:
retries += 1
time.sleep(2**retries)
print "Error (%d)... retrying." % e.resp.status
continue
print "Upload Complete!"
经过一番挖掘,我发现授权的http对象在收到401后会自动刷新访问令牌。虽然它确实在改变访问令牌,但它仍然没有按预期继续上传...请参阅下面的输出:
ya29.AHES6ZTo_-0oDqwn3JnU2uCR2bRjpRGP0CSQSMHGr6KvgEE
Uploaded 2.28%
ya29.AHES6ZTo_-0oDqwn3JnU2uCR2bRjpRGP0CSQSMHGr6KvgEE
Uploaded 2.29%
ya29.AHES6ZTo_-0oDqwn3JnU2uCR2bRjpRGP0CSQSMHGr6KvgEE
Uploaded 2.29%
ya29.AHES6ZTo_-0oDqwn3JnU2uCR2bRjpRGP0CSQSMHGr6KvgEE
Uploaded 2.30%
ya29.AHES6ZTo_-0oDqwn3JnU2uCR2bRjpRGP0CSQSMHGr6KvgEE
Error (401)... retrying.
ya29.AHES6ZQqp3_qbWsTk4yVDdHnlwc_7GvPZiFIReDnhIIiHao
Error (401)... retrying.
ya29.AHES6ZSqx90ZOUKqDEP4AAfWCVgXZYT2vJAiLwKDRu87JOs
Error (401)... retrying.
ya29.AHES6ZTp0RZ6U5K5UdDom0gq3XHnyVS-2sVU9hILOrG4o3Y
Error (401)... retrying.
ya29.AHES6ZSR-IOiwJ_p_Dm-OnCanVIVhCZLs7H_pYLMGIap8W0
Error (401)... retrying.
ya29.AHES6ZRnmM-YIZj4S8gvYBgC1M8oYy4Hv5VlcwRqgnZCOCE
Error (401)... retrying.
ya29.AHES6ZSF7Q7C3WQYuPAWrxvqbTRsipaVKhv_TfrD_gef1DE
Error (401)... retrying.
ya29.AHES6ZTsGzwIIprpPhCrqmoS3UkPsRzst5YHqL-zXJmz6Ak
Error (401)... retrying.
ya29.AHES6ZSS_1ZBiQJvZG_7t5uW3alsy1piGe4-u2YDnwycVrI
Error (401)... retrying.
ya29.AHES6ZTLFbBS8mSFWQ9zK8cgbX8RPeLghPxkfiKY54hBB-0
Error (401)... retrying.
ya29.AHES6ZQBeMWY50z6fWXvaCcd5_AJr_AYOuL2aiNKpK-mmyU
Error (401)... retrying.
ya29.AHES6ZTs2mYYSEyOqI_Ms4itKDx36t39Oc5RNZHkV4Dq49c
Retries limit exceeded! Aborting.
我正在使用安装了Python 2.5.2的debian lenny,并在大约一周前通过pip install安装了ssl和google-api-python-client。
提前感谢您的帮助。
编辑:显然,问题不在于api。我尝试了上面相同的代码,但有两个小文件,它们之间有1h(system.sleep())。输出是:
ya29.AHES6ZRUssiLfuhqCP9Cu7C7LuhRV2rYzPldU27wiMJZWb8
Uploaded 66.89%
ya29.AHES6ZRUssiLfuhqCP9Cu7C7LuhRV2rYzPldU27wiMJZWb8
Upload 1 Complete!
ya29.AHES6ZRUssiLfuhqCP9Cu7C7LuhRV2rYzPldU27wiMJZWb8
Uploaded 57.62%
ya29.AHES6ZQd3o1ciwXpNFImH3CK0-dJAtQba_oeIO9DDbIq154
Upload 2 Complete!
对于第二次上传,成功使用了新的访问令牌。那么,也许可恢复会话在一段时间后到期或者仅对该特定访问令牌有效?
答案 0 :(得分:4)
我提交了issue on the google-api-python-client project,根据谷歌的Joe Gregorio的说法,问题在于后端:
“这是后端的问题,而不是API或您的代码。正如您所推断的,如果上传时间太长,access_token将过期,此时无法继续恢复上传。有工作目前正在修复此问题的进展,一旦在服务器端修复了问题,我将更新此错误。“
答案 1 :(得分:0)
我认为问题是在1-2小时限制后,您的远程数据库的访问令牌到期;切断与远程服务器的连接。我认为你能做的就是查看你的主机API手册......他们应该有关于'刷新令牌'的内容(他们会得到另一个访问令牌,注意一些主机只允许你在每个会话中使用一个刷新令牌),如果他们被允许无限量,你可以使用计时器和AJAX的组合来继续要求更多访问令牌。
如果没有,那么您将为另一个授权令牌发出一个AJAX请求,并且每小时为另一个访问令牌交换该请求。这听起来像是一个非常严格的过程,但我认为这是唯一的方法,如果你的令牌持续到期。
另外,您还尝试过其他上传方法吗?如果您说上面的脚本运行了1-2个小时,它只上传了1.44%的文件,可能需要100多个小时才能完全上传(对于只有3个演出来说太长了)。