On Jan 6, 2014, at 5:56 PM, Nikolaus Rath <[email protected]> wrote:
> On 01/06/2014 09:36 AM, Diogo Vieira wrote:
>> On Jan 6, 2014, at 5:30 PM, Nikolaus Rath <[email protected]> wrote:
>>
>>> On 01/06/2014 02:13 AM, Diogo Vieira wrote:
>>>>> I am attempting to create an S3 filesystem and I am receiving the
>>>>> following error:
>>>>>
>>>>> "Invalid credentials or skewed system clock."
>>>>>
>>>>> Information about my setup:
>>>>>
>>>>>>> mkfs.s3ql --version
>>>>>>> S3QL 1.12
>>>>>
>>>>> Not my real values but just to make sure I am not making a mistake
>>>>> with parameters.
>>>>>
>>>>> Access Key ID: BA8AHD760HA1ZXDJUZPR
>>>>> Secret Access Key: valDQ8yuckEKzKVgxeHZRewcWb8zHVrVlezLyzPH
>>>>> Bucket Name: 4CB68BE999C642FB
>>>>>
>>>>>>> mkfs.s3ql s3://4CB68BE999C642FB
>>>>>>> Enter backend login: BA8AHD760HA1ZXDJUZPR
>>>>>>> Enter backend password: valDQ8yuckEKzKVgxeHZRewcWb8zHVrVlezLyzPH
>>>>>>> Invalid credentials or skewed system clock.
>>>>>
>>>>> To rule out the skewed clock I ran:
>>>>>
>>>>>>> ntpdate -q pool.ntp.org <http://pool.ntp.org/>
>>>>> server 216.129.110.30, stratum 2, offset -0.007092, delay 0.05629
>>>>> server 72.8.140.222, stratum 2, offset -0.003913, delay 0.10594
>>>>> server 165.123.132.61, stratum 2, offset -0.011243, delay 0.08008
>>>>> server 173.248.148.27, stratum 2, offset -0.005386, delay 0.10223
>>>>> 18 Oct 23:14:08 ntpdate[16126]: adjust time server 216.129.110.30
>>>>> offset -0.007092 sec
>>>>>
>>>>> Anyone see any problems with what I am doing?
>>>>
>>>> I have exactly the same problem. Can someone help me?
>>>
>>> Do your credentials work when you use a different program, e.g. s3cmd or
>>> http://timkay.com/aws/?
>>
>> It does, at least with s3cmd.
>
> Hm. Does it work if you put the credentials in ~/.s3ql/authinfo2? Also,
> please make 120% sure that you use exactly the same credentials and
> bucket name as for s3cmd. It would be pretty weird if S3QL's S3
> authentication would fail for you but work for everyone else…
Firstly I apologise, but made a mistake earlier in the bucket name. I missed a
character. But I have some other problems as well.
Now with the correct bucket name it did not give me the wrong credentials error
but instead kept bouncing around between servers ending with a "Too many
chained redirections" traceback as noted below:
Using proxy 10.10.4.254:3128
Using proxy 10.10.4.254:3128
_do_request(): redirected to s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to eurotux-teste2.s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to eurotux-teste2.s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to eurotux-teste2.s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to eurotux-teste2.s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to s3.amazonaws.com
Using proxy 10.10.4.254:3128
_do_request(): redirected to eurotux-teste2.s3.amazonaws.com
Uncaught top-level exception:
Traceback (most recent call last):
File "bin/mkfs.s3ql", line 26, in <module>
s3ql.mkfs.main(sys.argv[1:])
File "/home/dfv/s3ql-2.7/src/s3ql/mkfs.py", line 98, in main
plain_backend = get_backend(options, plain=True)
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 1407, in
get_backend
return get_backend_factory(options, plain)()
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 1479, in
get_backend_factory
backend.fetch('s3ql_passphrase')
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 443, in fetch
return self.perform_read(do_read, key)
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 67, in wrapped
return method(*a, **kw)
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 416, in
perform_read
with self.open_read(key) as fh:
File "/home/dfv/s3ql-2.7/src/s3ql/backends/common.py", line 67, in wrapped
return method(*a, **kw)
File "/home/dfv/s3ql-2.7/src/s3ql/backends/s3c.py", line 229, in open_read
resp = self._do_request('GET', '/%s%s' % (self.prefix, key))
File "/home/dfv/s3ql-2.7/src/s3ql/backends/s3c.py", line 305, in _do_request
raise RuntimeError('Too many chained redirections')
RuntimeError: Too many chained redirections
BTW, although I have the authfile in place it always asked for my credentials
again, unless I specified its path in with the flag --authfile (I don't know if
it intended).
Furthermore, the same traceback is show if I just hit <enter> in the
credentials field. As you should have noticed now I'm behind a proxy. I don't
know if it matters but I forgot to mention it. This is the authfile in case
it's intereting (I just changed the credentials fields):
[s3]
storage-url:s3://
backend-login:<access-key>
backend-password:<secret>
I am also absolutely sure I used the same credentials for both of the programs
(s3ql and s3cmd) and not only it did successfully connected to the server, but
I could list the available objects inside the bucket I was trying to access
with s3ql, along with other operations like listing the buckets, for example.
--
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/groups/opt_out.
