|
Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: bluedelta on December 12, 2007, 03:39:54 PM I've done something similar while experimenting, and now I'm stuck with a couple of test buckets I can't empty or delete.
When I run "s3cmd.rb deleteall bucketname" on one of these buckets I eventually get "S3 command failed" and "With result 500 Internal Server Error", and it goes into retry mode. I can list the contents of the bucket, and and running deleteall with -vd shows "Response code: 204" which is apparently a good thing - but the files don't actually get deleted. S3fox is flummoxed, so I can't use it either. How can I kill these apparently bulletproof buckets once and for all? Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: ferrix on December 12, 2007, 09:01:58 PM Ideally you'd use the deletebucket verb. deleteall is just a simple loop of delete's, and delete is for nodes not buckets.
Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: bluedelta on December 13, 2007, 01:12:03 AM Sorry, I failed to mention that - when I use deletebucket I get:
S3 command failed: delete_bucket With result 409 Conflict Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: ferrix on December 13, 2007, 09:08:41 AM OK so it sounds like for some reason there are items stuck and not able to be deleted, in 2 different tools too. Unless you want to give me access to your bucket I think you'll have to talk to AWS.
Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: bluedelta on December 13, 2007, 01:16:40 PM There is nothing of value in the buckets, just some directories and test files I was experimenting with. I'm happy to give you access, please let me know what username I should add to the ACL.
Title: Re: prefix may contain leading slash, but s3fox doesn't play nice Post by: ferrix on December 14, 2007, 07:02:45 PM I am greg13070
|