uploading file to s3 results in error 104 (connection reset)

[mjpan]

this is on boto 2.27.0. uploading a 14 byte file works, but 512k file causes this error.
using aws cli to upload works on the 512k file

File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/key.py", line 1315, in set_contents_from_filename
encrypt_key=encrypt_key)
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/key.py", line 1246, in set_contents_from_file
chunked_transfer=chunked_transfer, size=size)
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/key.py", line 725, in send_file
chunked_transfer=chunked_transfer, size=size)
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/key.py", line 914, in _send_file_internal
query_args=query_args
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/connection.py", line 633, in make_request
retry_handler=retry_handler
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/connection.py", line 1046, in make_request
retry_handler=retry_handler)
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/connection.py", line 919, in _mexe
request.body, request.headers)
File "/usr/local/lib/python2.7/dist-packages/boto-2.27.0-py2.7.egg/boto/s3/key.py", line 815, in sender
http_conn.send(chunk)
File "/usr/lib/python2.7/httplib.py", line 794, in send
self.sock.sendall(data)
File "/usr/lib/python2.7/ssl.py", line 229, in sendall
v = self.send(data[count:])
File "/usr/lib/python2.7/ssl.py", line 198, in send
v = self._sslobj.write(data)
error: [Errno 104] Connection reset by peer

[fbeister]

Just wanted to say "me too". I use boto through duplicity to access S3. On another machine, I have boto 2.2.2 and it works there. After downgrading boto from 2.27 to 2.2.2, the error persists, so I suspect the problem to lie either in ssl.py or the OS (Ubuntu Linux 14.04)

[fbeister]

Found a solution (at least for duplicity):
aws/aws-cli#634

instead of "s3+http://bucketname" use "s3:///s3.amazonaws.com/bucketname"

[danielgtaylor]

From the CLI issue:

I'm reopening this issue. After debugging this I can confirm what others have said. This problem exists when trying to upload a large file to a newly created bucket that's not in the classic region.

From what I can tell the CLI is properly retrying requests and following 307 redirects. The problem, however, is that the CLI sends the entire request and then waits for a response. However, S3 will immediately send the 307 response before we've finished sending the body. Eventually it will just close the connection, and if we're still in the process of streaming the body, we will not see the response. Instead we get the ConnectionError as shown in the various debug logs above.

The normal way to address this would be to use the expect 100 continue header. However, the HTTP client we use (requests) does not support this. There might be a way to work around this, but I'll need to do some digging into the requests library to see the best way to fix this issue.

This will require adding some support for currently unsupported HTTP headers.

[avandendorpe]

I think the fix for awscli addresses this as it was merged in botocore. @jamesls - is that correct?

[danielgtaylor]

The fix for Botocore was in boto/botocore@9e59c4e and seems to have solved the issue.

We need to backport it to Boto. I'll see about trying to get it into the next release.

[j0hnsmith]

I'm seeing a lot of these errors, please backport the fix asap.

[unwitting]

@danielgtaylor any update on getting it ported back into boto?

[jvantuyl]

+1

[anna-buttfield-sirca]

This issue hit us too. The workaround that worked for us was explicitly connecting to the bucket's region. Because we can't guarantee which region buckets are in we use this code:

conn = boto.connect_s3()
bucket = conn.get_bucket(bucket_name)
bucket_location = bucket.get_location()
if bucket_location:
    conn = boto.s3.connect_to_region(bucket_location)
    bucket = conn.get_bucket(bucket_name)

[charles-vdulac]

+1

[gpg90]

+1

[whitequark]

+1

[dwijnand]

👍

[eberle1080]

+1

[wengole]

This doesn't quite work as regions and locations have different names, however the concept does help (connecting to the correct region)

[fangpenlin]

+1

[volnt]

+1

[hwkns]

+1

[antonagestam]

Come on ppl, commenting +1 isn't helping anyone.

[hwkns]

@antonagestam, my intent was to help provide a sense of the number of people affected by this bug, which should hopefully lend it some priority. If there's something more I can do to help, please let me know. This is a sponsored project now, and this issue has been around for at least 9 months already, affecting quite a few users. I'm just trying not to let it languish.

[hellwolf]

+1

[ledmonster]

+1

[spikewilliams]

I am hitting this bug. Just as someone referenced above, I am also on Ubuntu Linux 14.04.

[slavpetroff]

Hello guys! The solution for me was first, to change S3 Location from Frankfurt to London. Then additionally i've added AWS_S3_HOST = 's3-eu-west-2.amazonaws.com' to the settings files and this solved my problem. Hope this helps!

[dvl]

@ilmesi solution from 2 years ago still working on latest boto version... so next time I found this issue on Google I know what to do.

[jcampbell05]

:) 2017 and this still needed to be used as a workaround.

[karthikvadla]

@jcampbell05 I see the same error

error: [Errno 104] Connection reset by peer

i'm trying to upload files from my local machine to s3 using boto.
I'm using set_contents_from_filename(filename). It's failing for data which is morethan 5GB.

did you use upload_file from boto3. What workaround did you use.?

[jcampbell05]

Rolling back my entire server to an older OS and version of boto. Not really a long term viable solution.

[shanx]

If you want to transfer files > 5gb you need to use multipart uploading (unfortunately boto2 doesn't abstract this away from us). I've done an implementation for this using the example from: http://boto.cloudhackers.com/en/latest/s3_tut.html#storing-large-data in the bakthat project (a project similar to duplicity) see my pull request tsileo/bakthat#84

[karthikvadla]

@jcampbell05 @shanx : Thank you for your responses. I migrated from boto2.x to boto3(which has in-built support for mutlipart file upload with upload_file feature. ). I followed this.
http://boto3.readthedocs.io/en/latest/reference/services/s3.html#S3.Client.upload_file .
Which made my work simple and easier. And i tested, it works fine. :)

[tambakoo]

So is this resolved ? I still cannot push a 1.9GB file to s3 from an ec2 . Gets a ConnectionResetError(104, 'Connection reset by peer')

[jcampbell05]

@tambakoo short answer is this isn't supported in boto2 upgrade to boto3 to get a method which supports large files :)

[kenny1323]

On ubuntu 18
Install python 3
sudo apt-get install python3-pip
pip3 install awscli --upgrade --user
aws s3 sync ./ s3://mybucket01

https://linuxhint.com/install_aws_cli_ubuntu/
https://linuxhint.com/install_aws_cli_ubuntu/

[StanSilas]

@tambakoo How did you resolve it?

[jcampbell05]

short answer is this isn't supported in boto2 upgrade to boto3 to get a method which supports large files :)

@StanSilas
See above 😀

[jiangwei-yu-pony]

Amazing to find out the solution (setting the region name) in a 9-year old thread!