Amazon S3: s3cmd put ([Errno 32] Broken pipe)
Read OriginalThe article details a specific technical issue encountered when uploading a 238MB backup file to a new Amazon S3 bucket using the s3cmd tool, resulting in '[Errno 32] Broken pipe' and '[Errno 104] Connection reset by peer' errors. It explains the troubleshooting process and identifies the root cause as DNS propagation delays for new buckets, with the solution being to wait a few hours before the upload succeeds.
0 comments
![Amazon S3: s3cmd put ([Errno 32] Broken pipe)](https://alldevblogs.blob.core.windows.net/thumbs/article-069960747244-full-f5447f82.webp)
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet