On Jun 29 2015, Andy Cress <[email protected]> wrote:
> We had a user attempt to do mkfs.s3ql via s3c to an OBS CleverSafe backend.
> It got the error backtrace below.
> Any known issues with CleverSafe?   If not, thoughts on what might be wrong?
>
> Failed to make filesystem at 
> s3c://obs.thebunker.net:443/com.tvgmedia.unitrends
> Before using S3QL, make sure to read the user's guide, especially the
> 'Important Rules to Avoid Loosing Data' section.
> Uncaught top-level exception:
> Traceback (most recent call last):
>   File "/usr/bin/mkfs.s3ql", line 9, in <module>
>     load_entry_point('s3ql==1.17', 'console_scripts', 'mkfs.s3ql')()
>   File 
> "/usr/lib64/python2.7/site-packages/s3ql-1.17-py2.7-linux-x86_64.egg/s3ql/mkfs.py",
> line 102, in main
>     if 's3ql_metadata' in plain_backend:
>   File 
> "/usr/lib64/python2.7/site-packages/s3ql-1.17-py2.7-linux-x86_64.egg/s3ql/backends/common.py",
> line 236, in __contains__
>     return self.contains(key)
>   File 
> "/usr/lib64/python2.7/site-packages/s3ql-1.17-py2.7-linux-x86_64.egg/s3ql/backends/common.py",
> line 356, in contains
>     self.lookup(key)
>   File 
> "/usr/lib64/python2.7/site-packages/s3ql-1.17-py2.7-linux-x86_64.egg/s3ql/backends/common.py",
> line 63, in wrapped
>     return fn(self, *a, **kw)
>   File 
> "/usr/lib64/python2.7/site-packages/s3ql-1.17-py2.7-linux-x86_64.egg/s3ql/backends/s3c.py",
> line 241, in lookup
>     assert resp.length == 0
> AssertionError

Looks like OBS Clever Safe answers HEAD requests with a non-zero
response body. This violates RFC2616, see 
https://tools.ietf.org/html/rfc2616#section-9.4.

Apart from that, you're also using a very outdated S3QL version.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to