-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
purge-vault not working #32
Comments
hi. try vault name "Videos"
|
Not sure I understand. That's the vault name I'm using. |
The whole command I'm using is: mtglacier purge-vault --config=/root/glacier.cfg --to-vault=Videos --journal=/root/glacier-journal.log |
Ok. Then it should work :( Maybe it's permission issue (check minimum permission example in the bottom Or maybe yo've just created that vault and amazon failed to delete archives I believe you can try contact Amazon (for example here Unfortunately I cannot help currently with testing again this mtglacier 2013/4/20 telscuba notifications@github.com
|
Hello. So, were you able to resolve this? |
Thanks. I saw that in my original Google search. I haven't resolved it On Fri, Apr 26, 2013 at 7:58 AM, Victor Efimov notifications@github.comwrote:
|
Hm. Interesting. If deletion one-by-one works, then the issue cannot be explained by Amazon problem. Thanks. I'll try to think how could this happen.. |
I've tested purge-vault in latest version - it works fine for me. |
I appreciate it, and thanks for the follow up! I'll also get the latest On Fri, Apr 26, 2013 at 9:14 AM, Victor Efimov notifications@github.comwrote:
|
latest - I meant 0.942beta - you already have it. |
Hi. I posted to Amazon forums |
I did, indeed, use the same journal for all my vaults. I didn't know that On Sun, Apr 28, 2013 at 10:08 PM, Victor Efimov notifications@github.comwrote:
|
Ok, cool. For every command you should explicit specify vault and region (including sync and purge-vault), and you should use same vault/region with one journal. Journal does not contain region/vault names. I will add to documentation explanation what Journal is, and will include explicit clarification that user should maintain region/vault/journal relation by himself (it's can be easy, if you specify region/vault/journal in one config file and don't change it, or if you include region+vault names in name of your journal file) BTW You can use Or maybe you won't have to purge vault after Thanks for reporting! |
FYI Documentation section "Journal Concept" is added https://github.com/vsespb/mt-aws-glacier#journal-concept |
Your follow up is nothing short of awesome. Thank you for this software and Sent from my iPhone On Apr 30, 2013, at 11:43 AM, Victor Efimov notifications@github.com FYI Documentation section "Journal Concept" is added — |
:) Thanks! |
Not certain if this is an mt-aws-glacier issue or an Amazon Glacier issue.
I issued the purge-vault command, and got this error:
HTTP/1.1 400 Bad Request
Date: Sat, 20 Apr 2013 15:55:17 GMT
Content-Length: 142
Content-Type: application/json
Client-Date: Sat, 20 Apr 2013 15:55:17 GMT
Client-Peer: 204.246.163.151:80
Client-Response-Num: 1
X-Amzn-RequestId: VzMhvWr63bsqtDaRYGLbQ38v5fXK8rcwP5lIhtHPUCW0SkQ
{"code":"InvalidParameterValueException","message":"Invalid vault name: arn:aws:glacier:us-west-1:954508486505:vaults/Videos","type":"Client"}
PARENT Exit
DELETE http://glacier.us-west-1.amazonaws.com/-/vaults/Videos/archives/wLl1mzek-1O4jlgVGS_B7WMY2Ailw1-YQZvVioOmyipQlbgWJzihNtvQccrBe8cmVauJcGNyIzPxY_FZduDKtXyRmgwFMOTlBgECjNpuc5METK1M5ymK1q3dm9lP97C7Gh5jSQY2NQ
Authorization: AWS4-HMAC-SHA256 Credential=XXXXXXXXXXXXXXXXXX/20130420/us-west-1/glacier/aws4_request, SignedHeaders=host;x-amz-date;x-amz-glacier-version, Signature=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Host: glacier.us-west-1.amazonaws.com
User-Agent: mt-aws-glacier/0.942beta (http://mt-aws.com/) libwww-perl/5.836
X-Amz-Date: 20130420T155515Z
X-Amz-Glacier-Version: 2012-06-01
It looks to me, though, that the name "arn:aws:glacier:us-west-1:954508486505:vaults/Videos" is truly valid, as I look at my glacier account.
The text was updated successfully, but these errors were encountered: