-
Notifications
You must be signed in to change notification settings - Fork 232
Tips
Andrew Gaul edited this page Dec 23, 2017
·
4 revisions
Authentication misconfiguration can cause spurious client failures. Ensure that you have NTP enabled on all machines. If all else fails you can disable s3proxy authentication via:
s3proxy.authorization=none
You can use curl to debug s3proxy when authentication is disabled (see above):
- list containers in a storage account:
curl http://<proxy>/ - list blobs in a container:
curl http://<proxy>/<containername> - add a new container:
curl -X PUT http://<proxy>/<newcontainername> - add a new blob to a container:
curl -X PUT -T <filename> http://<proxy>/<containername>/<newblobname>
Debug logging reveals more information about requests:
java -DLOG_LEVEL=debug -jar s3proxy.jar
Trace logging shows the client requests and server responses:
java -DLOG_LEVEL=trace -jar s3proxy.jar
Emit storage backend requests and responses:
java -DLOG_LEVEL=trace -Djclouds.wire=debug -jar s3proxy.jar