I've worked with Mike offline on this some today, and believe I have a fix
now on the github.com/s3tools/s3cmd master branch.
The failure here was a timeout on a batch delete call to S3 that included
roughly 40,000 files in the single batch delete request, rather than the
1000 per request that the
Please ignore this. I was observing aws cli - not s3cmd when I saw this.
Mike
On Apr 10, 2014, at 5:11 PM, WagnerOne wrote:
> Mostly just an observation to report... occasionally when I stop s3cmd with
> ctrl-c when also running under --dry-run, I'll see a
>
> "Cleaning up. Please wait..."
>
Mostly just an observation to report... occasionally when I stop s3cmd with
ctrl-c when also running under --dry-run, I'll see a
"Cleaning up. Please wait..."
"Completed parts..."
And then it hangs indefinitely until I kill the process. This seems to happen
more often with dry-run than it
Running this same sync in debug, I see additional detail following the "INFO:
Summary: ..." line.
I'm not sure what I should anonymize in that output, so I'd prefer to share it
with a dev only. I can produce that on request.
Mike
On Apr 10, 2014, at 3:21 PM, WagnerOne wrote:
> Hi,
>
> Encou
Hi,
When attempting to s3cmd sync 2 buckets today, I encountered this "An
unexpected error has occurred." output from s3cmd itself.
I am using the latest available s3cmd master branch code via a git clone
(updated today).
I tried this several times within the 2 same buckets on different prefi
Hi,
Encountered what appears to be a bug today.
I am syncing a local directory and an s3 prefix that I have not been in control
of (unlike the many other s3cmd syncs I have done successfully).
When trying to sync existing local directories with prefixes in this bucket, I
am encountering 2 thi