1. David Larlet
  2. django-storages
  3. Issues

Issues

Issue #114 new

[s3boto] SSLError: [Errno 6] _ssl.c:503: TLS/SSL connection has been closed

tomwys
created an issue

I have this error multiple times. My setup is EC2 + S3 (Europe). If you have any questions that can help to fix this issue please contact me.

{{{ SSLError: [Errno 6] _ssl.c:503: TLS/SSL connection has been closed

Stacktrace (most recent call last):

[I have cut uninteresting django template rendering]

File "compressor/templatetags/compress.py", line 86, in render cache_key, cache_content = self.render_cached(compressor, forced)

File "compressor/templatetags/compress.py", line 65, in render_cached compressor, self.mode, self.kind)

File "compressor/cache.py", line 81, in get_templatetag_cachekey "templatetag.%s.%s.%s" % (compressor.cachekey, mode, kind))

File "compressor/utils/decorators.py", line 39, in get value = obj.dict[self.name] = self.__get(obj)

File "compressor/base.py", line 120, in cachekey [self.content] + self.mtimes).encode(self.charset), 12)

File "compressor/utils/decorators.py", line 39, in get value = obj.dict[self.name] = self.__get(obj)

File "compressor/base.py", line 114, in mtimes for kind, value, basename, elem in self.split_contents()

File "compressor/js.py", line 22, in split_contents filename = self.get_filename(basename)

File "compressor/base.py", line 73, in get_filename if self.storage.exists(basename):

File "storages/backends/s3boto.py", line 209, in exists return k.exists()

File "boto/s3/key.py", line 360, in exists return bool(self.bucket.lookup(self.name))

File "boto/s3/bucket.py", line 147, in lookup return self.get_key(key_name, headers=headers)

File "boto/s3/bucket.py", line 167, in get_key query_args=query_args)

File "boto/s3/connection.py", line 423, in make_request override_num_retries=override_num_retries)

File "boto/connection.py", line 618, in make_request return self._mexe(http_request, sender, override_num_retries)

File "boto/connection.py", line 572, in _mexe raise e }}}

Comments (2)

  1. Log in to comment