aws 无凭据错误

aws no credentials error

我正在尝试设置动态缩略图服务 thumbor and to support s3 as storage, I need to setup this community powered pip library for aws

它在我的本地环境中运行良好,但是当我尝试将它托管在我们的一台服务器上时,我收到 NoCredentialsError。我假设这是因为 botocore 的不同版本(最新版本和 pip 库安装的版本)。这是错误日志:

  File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 774, in get_component
    # client config from the session
  File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 174, in <lambda>
    self._components.lazy_register_component(
  File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 453, in get_data
    - agent_version is the value of the `user_agent_version`
  File "/usr/local/lib/python2.7/dist-packages/botocore/loaders.py", line 119, in _wrapper
    data = func(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/loaders.py", line 364, in load_data
DataNotFoundError: Unable to load data for: _endpoints







2016-04-24 12:14:34 tornado.application:ERROR Future exception was never retrieved: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 230, in wrapper
    yielded = next(result)
  File "/usr/local/lib/python2.7/dist-packages/thumbor/handlers/imaging.py", line 31, in check_image
    exists = yield gen.maybe_future(self.context.modules.storage.exists(kw['image'][:self.context.config.MAX_ID_LENGTH]))
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 455, in wrapper
    future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 215, in result
    raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 443, in wrapper
    result = f(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tc_aws/aws/storage.py", line 107, in exists
    self.storage.get(file_abspath, callback=return_data)
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 455, in wrapper
    future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 215, in result
    raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 443, in wrapper
    result = f(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tc_aws/aws/bucket.py", line 44, in get
    Key=self._clean_key(path),
  File "/usr/local/lib/python2.7/dist-packages/tornado_botocore/base.py", line 97, in call
    return self._make_api_call(operation_name=self.operation, api_params=kwargs, callback=callback)
  File "/usr/local/lib/python2.7/dist-packages/tornado_botocore/base.py", line 60, in _make_api_call
    operation_model=operation_model, request_dict=request_dict, callback=callback)
  File "/usr/local/lib/python2.7/dist-packages/tornado_botocore/base.py", line 54, in _make_request
    request_dict=request_dict, operation_model=operation_model, callback=callback)
  File "/usr/local/lib/python2.7/dist-packages/tornado_botocore/base.py", line 32, in _send_request
    request = self.endpoint.create_request(request_dict, operation_model)
  File "/usr/local/lib/python2.7/dist-packages/botocore/endpoint.py", line 126, in create_request
    operation_name=operation_model.name)
  File "/usr/local/lib/python2.7/dist-packages/botocore/hooks.py", line 226, in emit
    return self._emit(event_name, kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/hooks.py", line 209, in _emit
    response = handler(**kwargs)
  File "/usr/local/lib/python2.7/dist-packages/botocore/signers.py", line 90, in handler
    return self.sign(operation_name, request)
  File "/usr/local/lib/python2.7/dist-packages/botocore/signers.py", line 124, in sign
    signer.add_auth(request=request)
  File "/usr/local/lib/python2.7/dist-packages/botocore/auth.py", line 626, in add_auth
    raise NoCredentialsError
NoCredentialsError: Unable to locate credentials

是否可以通过我安装库的正确顺序来修复它?因为 pip 库删除了现有的较新版本的 botocore 并安装了旧版本。

编辑:

我是 运行 主管的进程,似乎进程无法访问 aws 凭据

编辑 2:

问题已通过正确配置 supervisor 得到解决。主管启动的进程的用户无权访问配置文件

问题已通过正确配置 supervisor 得到解决。主管启动的子进程的用户无权访问 aws 配置文件。所以它正在与本地环境一起工作或单独创建过程而不是与主管一起工作。