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 things I've not seen before using s3cmd. One is during sync preparation "WARNING: Empty object name on S3 found, ignoring." and is obviously intended and seemingly innocuous. The other is "ERROR: timed out" when s3cmd gets to the point of beginning the deletes and/or transfers as needed. I've not encountered a time out before. If I delete the prefix entirely on the bucket side and issue the same s3cmd command again, it sync fine. Makes me wonder if the deletion step is choking on the "empty object" that was found (which I believe I understand from research is objects deleted manually via the AWS web gui). INFO: Retrieving list of remote files for s3://mybucket/myprefix/ ... WARNING: Empty object name on S3 found, ignoring. INFO: Found 788889 local files, 75128 remote files INFO: Verifying attributes... INFO: Summary: 763456 local files to upload, 0 files to remote copy, 49694 remote files to delete ERROR: timed out I'm running my s3cmd via a git clone of the master branch from github (fresh pull today). Mike -- wag...@wagnerone.com "Good music is good no matter what kind of music it is."-Miles Davis ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ S3tools-general mailing list S3tools-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/s3tools-general
