S3cmd failed with Error Code 74 when uploading to Amazon S3
My backup to Amazon S3 started failing Tuesday morning. This is the command
Code:
s3cmd sync --delete-removed --limit-rate=288K --multipart-chunk-size-mb=5 --no-progress LOCAL_DIR s3://BUCKET Quote:
Hope this helps someone. |
Well it failed again today for same reason.
In the eight or more years of running s3cmd never had this error. Seemed to fix it after increasing the transfer rate. In the past had problems with the chunk rate, in the past had to decrease it. Investigation continues. |
After more than a month with error free syncing with aws it failed again yesterday morning and again this morning
Quote:
I've posted a query to the S3cmd mailing list. My post never got onto the list. Anyway as I've said previously if I fed the data piecemeal directory by directory that's worked in the past when I get these 74 errors I've also now found that if is use the awscli package, from SlackBuilds.org, instead of s3cmd package, from SlackBuilds.org, and change my call from Code:
s3cmd sync $DRYRUN ${DEBUG_STRING} --delete-removed ${LIMITRATE} ${CHUNKSIZE} ${PROGRESS} myfolder s3://mybucket/myfolder Code:
aws s3 sync --delete myfolder s3://mybucket/myfolder I shall try again to post to the s3cmd forum mailing list, there's only been 3 postings this year which probably explains why my posting of a month or so ago got missed. |
Posted a bug report with the people at s3cmd.
Also found another workaround for this "feature" which only raises an error when it's deleting loads of objects from a bucket. The ensures that the whole bucket isn't inadvertently emptied. There might be an undocumented limit of 1,000 objects and if it hits this it bombs out with the 74 error code. My workaround was to -
|
All times are GMT -5. The time now is 11:34 AM. |