This page is intended to record some tips and procedures used to gather information about s3sync problems, to assist in debugging.
Use -n -v and -d
Use tcpdump or wireshark
Please be advised that any confidential information in the data you transfer will be plainly visible to anyone who views the capture file.
- Do not use -s because then traffic will be encrypted, and un-debug-able.
- tcpdump -p -s 0 -w tcpdump.cap -i eth0
Unexpected 403 Forbidden messages
If you are getting 403 Forbidden messages that look like this:
S3 command failed: get_stream BucketName ObjectName #<File:0xb7d31e24> With result 403 Forbidden
And you've made sure your access and secret keys are correct, you might want to check the time on your machine, as that can cause failures.
Every file gets transferred on every sync
"If I resync the same directory repeatedly, the same files get copied over and over:"
martin@dev$ s3sync/s3sync.rb test/ bucketname:/test/ -v Create node test1 Create node test2 Create node test3 Create node test4 Create node test5 martin@dev$ s3sync/s3sync.rb test/ bucketname:/test/ -v Create node test1 Create node test2 Create node test3 Create node test4 Create node test5
The solution is to ensure that neither your source nor your destination path ends in a slash, and no slashes at all in your destination path, e.g.
s3sync/s3sync.rb /leading/directories/are/ok/test bucketname:test -v