February 02, 2014, 01:19:36 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
   Home   Help Search Login Register  
Pages: [1]
Author Topic: s3sync fails on 400 Bad Request  (Read 2677 times)
Posts: 1

View Profile
« on: February 02, 2011, 03:47:01 PM »

I'm uploading a tree of a few thousand files to S3. Some files don't make it up (I don't have a pattern for which ones make it and which don't).

In this case, a file in that tree didn't make it up, and it said so in the logs. Is there a way to make it retry on 400?

Here is the relevant output:

$ s3sync.rb -p --make-dirs -r ~/v/ dest:dir/vtest3/ 2>&1 | tee s3sync2.out
S3 command failed:
put dir/vtest3/test.swf #<S3::S3Object:0x102240600> x-amz-acl public-read Content-Type application/x-shockwave-flash Content-Length 30226
With result 400 Bad Request
Sr. Member
Posts: 363

(I am greg13070 on AWS forum)

View Profile
« Reply #1 on: February 03, 2011, 08:28:13 AM »

Usually a 400 error means the client side has done something wrong, so that's why we don't just keep retrying it.  (Retries are done to 500 errors because amazon asks us to). 

If you want to change the range of errors we retry on, go into s3try.rb and change

break unless ((500...600).include? result.http_response.code.to_i) or forceRetry

to be 400...600 (for example)
Pages: [1]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!