Hi Greg,
I’m guessing that something isn’t running. Try the following (without the back
checks) and see if you get “pong” for each one:
`riak ping`
`riak-cs ping`
`stanchion ping`
You may or may not need `sudo` to execute the above depending on the user you
are using.
Incidentally, your s3cfg file looks incredibly short. Here is my standard one:
access_key = admin.key
bucket_location = US
cloudfront_host = cloudfront.amazonaws.com
cloudfront_resource = /2010-07-15/distribution
default_mime_type = binary/octet-stream
delete_removed = False
dry_run = False
encoding = UTF-8
encrypt = False
follow_symlinks = False
force = False
get_continue = False
gpg_command = /usr/bin/gpg
gpg_decrypt = %(gpg_command)s -d --verbose
--no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o
%(output_file)s %(input_file)s
gpg_encrypt = %(gpg_command)s -c --verbose
--no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o
%(output_file)s %(input_file)s
gpg_passphrase =
guess_mime_type = True
host_base = s3.amazonaws.com
host_bucket = %(bucket)s.s3.amazonaws.com
human_readable_sizes = False
list_md5 = False
log_target_prefix =
preserve_attrs = True
progress_meter = True
proxy_host = 127.0.0.1
proxy_port = 18080
recursive = False
recv_chunk = 4096
reduced_redundancy = False
secret_key = admin.secret
send_chunk = 4096
simpledb_host = sdb.amazonaws.com
skip_existing = False
socket_timeout = 10
urlencoding_mode = normal
use_https = False
verbosity = WARNING
signature_v2 = True
Of course, the admin.key and admin.secret are substituted out for appropriate
values.
Finally, what version of s3cmd are you using? If 1.x then you should be fine.
2.x is known to have a few difficulties with some functions but usually works.
We are hoping to rectify that in Riak CS 2.2.0.
Hope this helps,
Nicholas
From: riak-users <[email protected]> On Behalf Of Greg Zoller
Sent: 23 April 2019 23:43
To: [email protected]
Subject: Having trouble setting up riak-cs using s3cmd to test
Hello,
I'm following the instructions for the Docker-ized riak-cs. The Docker
container runs and (appears) healthy.
I am now testing the install with s3cmd as described in the instructions. I
installed s3cmd and am using this .s3cfg file: (the 2 keys I got from the
running container's log output as instructed)
[default]
access_key = Q9NKDXZJGAD2CZF3T4B7
host_base = s3.amazonaws.dev<http://s3.amazonaws.dev>
host_bucket = %(bucket)s.s3.amazonaws.dev<http://s.s3.amazonaws.dev>
proxy_host = localhost
proxy_port = 8080
secret_key = 2aR_IthHHYQpFGx8xP0z46ZyoQUsfzvSsTl4bA==
signature_v2 = True
When I run a simple command like "s3cmd ls" I get this output:
WARNING: Retrying failed request: / (No status line received - the server has
closed the connection)
WARNING: Waiting 3 sec...
WARNING: Retrying failed request: / (No status line received - the server has
closed the connection)
WARNING: Waiting 6 sec...
^CSee ya!
Any ideas what I'm doing wrong?
Thanks,
Greg
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
