Doing something stooopid. Please point it out:
authfile;
[swift]
backend-login:<tenant>:<user>
backend-password:<password>
storage-url: swiftks://<host>:<port>/<region>/<container> ## container
does exist, created with swift cli
mkfs command;
mkfs.s3ql --debug all --authfile .s3ql_auth --plain --cachedir /.s3ql_cache
swiftks://<host>:<port>/<region>/<container>
it still prompts for creds??
Enter backend login:
Enter backend passphrase:
I get a 401 and then a 'discard'. Note: I can see a valid token given by
my auth server on the backend while tailing the logs.
2014-04-17 16:00:25.465 9240 MainThread
s3ql.backends.common.get_ssl_context: Reading default CA certificates.
2014-04-17 16:00:25.476 9240 MainThread s3ql.backends.swift._do_request:
_do_request(): start with parameters ('GET', '/', None, {'limit': 1}, None,
None)
2014-04-17 16:00:25.476 9240 MainThread s3ql.backends.swift._do_request:
_do_request(): no active connection, calling _get_conn()
2014-04-17 16:00:25.476 9240 MainThread s3ql.backends.swiftks._get_conn:
_get_conn(): start
2014-04-17 16:00:25.476 9240 MainThread dugong.co_send_request: start
2014-04-17 16:00:25.477 9240 MainThread dugong.connect: start
2014-04-17 16:00:25.477 9240 MainThread dugong.connect: connecting to
('freaking valid host', port)
2014-04-17 16:00:30.620 9240 MainThread dugong.connect: establishing ssl
layer
2014-04-17 16:00:30.884 9240 MainThread dugong.connect: done
2014-04-17 16:00:30.885 9240 MainThread dugong.co_send_request: computing
content-md5
2014-04-17 16:00:30.885 9240 MainThread dugong.co_send_request: sending
POST /v2.0/tokens
2014-04-17 16:00:30.885 9240 MainThread dugong._co_send: trying to send 345
bytes
2014-04-17 16:00:30.885 9240 MainThread dugong._co_send: sent 345 bytes
2014-04-17 16:00:30.885 9240 MainThread dugong._co_send: done
2014-04-17 16:00:30.885 9240 MainThread dugong.co_read_response: start
2014-04-17 16:00:30.885 9240 MainThread dugong._co_read_status: start
2014-04-17 16:00:30.885 9240 MainThread dugong._co_readstr_until: reading
until b'\r\n'
2014-04-17 16:00:30.886 9240 MainThread dugong._try_fill_buffer: start
2014-04-17 16:00:30.886 9240 MainThread dugong._try_fill_buffer: done
(nothing ready)
2014-04-17 16:00:30.886 9240 MainThread dugong._co_readstr_until: need more
data, yielding
2014-04-17 16:00:30.886 9240 MainThread dugong.poll: calling poll
2014-04-17 16:00:31.014 9240 MainThread dugong.eval_coroutine: polling
2014-04-17 16:00:31.014 9240 MainThread dugong._try_fill_buffer: start
2014-04-17 16:00:31.014 9240 MainThread dugong._try_fill_buffer: done (got
201 bytes)
2014-04-17 16:00:31.014 9240 MainThread dugong._co_readstr_until: found
substr at 25
2014-04-17 16:00:31.014 9240 MainThread dugong._co_read_status: done
2014-04-17 16:00:31.014 9240 MainThread dugong.co_read_response: got 401
Unauthorized
2014-04-17 16:00:31.015 9240 MainThread dugong._co_read_header: start
2014-04-17 16:00:31.015 9240 MainThread dugong._co_readstr_until: reading
until b'\r\n\r\n'
2014-04-17 16:00:31.015 9240 MainThread dugong._co_readstr_until: found
substr at 197
2014-04-17 16:00:31.015 9240 MainThread dugong._co_read_header: done (174
characters)
2014-04-17 16:00:31.017 9240 MainThread dugong.co_read_response: identity
encoding detected
2014-04-17 16:00:31.017 9240 MainThread dugong.co_read_response: done
(in_remaining=131)
2014-04-17 16:00:31.017 9240 MainThread root.excepthook: Uncaught top-level
exception:
Traceback (most recent call last):
File "/usr/bin/mkfs.s3ql", line 9, in <module>
load_entry_point('s3ql==2.8.1', 'console_scripts', 'mkfs.s3ql')()
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/mkfs.py",
line 98, in main
plain_backend = get_backend(options, plain=True)
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/common.py",
line 1353, in get_backend
return get_backend_factory(options, plain)()
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/common.py",
line 1447, in get_backend_factory
ssl_context, proxy=proxy)
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/swiftks.py",
line 45, in __init__
self._container_exists()
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/common.py",
line 65, in wrapped
return method(*a, **kw)
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/swift.py",
line 70, in _container_exists
self._do_request('GET', '/', query_string={'limit': 1 })
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/swift.py",
line 179, in _do_request
self.conn = self._get_conn()
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/common.py",
line 65, in wrapped
return method(*a, **kw)
File
"/usr/lib64/python3.3/site-packages/s3ql-2.8.1-py3.3-linux-x86_64.egg/s3ql/backends/swiftks.py",
line 105, in _get_conn
self.conn.discard()
AttributeError: 'NoneType' object has no attribute 'discard'
--
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.
