We are getting this error report quite a lot lately. It's because s3cmd doesn't properly handle empty directories within buckets.  The original idea was that one could not have an empty directory, because the only things that could be referenced were objects (perhaps objects in a directory).  No object, no directory.  But then Amazon does have a way to create empty directories, and s3cmd doesn't know what to do with such.

I started a patch (https://github.com/mdomsch/s3cmd/tree/bug/174) but I don't think it's complete...  You're welcome to try and see if it works.

On Mon, Jul 15, 2013 at 3:45 PM, Jonathan Duncan <jonathan@nacnud.com> wrote:
Problem: OSError: [Errno 20] Not a directory
S3cmd:   1.5.0-alpha3

Traceback (most recent call last):
  File "/usr/local/bin/s3cmd", line 2094, in <module>
  File "/usr/local/bin/s3cmd", line 2034, in main
  File "/usr/local/bin/s3cmd", line 1193, in cmd_sync
    return cmd_sync_remote2local(args)
  File "/usr/local/bin/s3cmd", line 891, in cmd_sync_remote2local
    seq, total_size = _download(remote_list, seq, remote_count + update_count, total_size, dir_cache)
  File "/usr/local/bin/s3cmd", line 850, in _download
    raise e
OSError: [Errno 20] Not a directory

See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!