Jacob Tomlinson • 7/31/2014

Amazon S3: s3cmd put ([Errno 32] Broken pipe)

Read Original

The 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 #Upload Error
Amazon S3: s3cmd put ([Errno 32] Broken pipe)

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

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes