Well, that was it. I copied the sample PUT from the elasticsearch web
site, which of course uses curl, and did not take out the -d. Definitely
helps to have another pair of eyes. I was looking at that all day and
didn't see the -d. Thanks for your help.
Shawn
On Friday, June 13, 2014 5:35:45 AM UTC-6, Shawn Mullen wrote:
>
> good question. that is what is being returned when I make the call. but
> your question gave me an idea as to what the problem is.
>
> thanks.
> On Jun 12, 2014 11:32 PM, "David Pilato" wrote:
>
>> What is this -d in "statlogs -d"?
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>>
>> Le 13 juin 2014 à 03:58, Shawn Mullen
>>
>> I have an ElasticSearch instance running on my local machine. I
>> installed the S3 plugin so I can do backup and restore operation to/from S3.
>>
>> I tried to follow the documentation on how to set this up. I was able to
>> register a snapshot repository and I have a bucket in S3 created just for
>> backups. When I do a /_all I see the current repo settings. So, at this
>> point all looks fine. However, when I try to create a snapshot it fails
>> with RepositoryMissingException.
>>
>> This is what I get for a /_all:
>>
>> {
>> "statlogs -d": {
>> "type": "s3",
>> "settings": {
>> "region": "us-east",
>> "bucket": "<my-bucket-name>",
>> "access_key": "<my-access-key>",
>> "secret_key": "<my-secret-key>"
>> }
>> }
>> }
>>
>> This is what I am sending when I try to do a snapshot:
>>
>> PUT /_snapshot/statlogs/snapshot_1 -d
>> {
>> "indices": ["statexceptionlog"],
>> "ignore_unavailable": "true",
>> "include_global_state": false
>> }
>>
>> I am using Sense to send the commands.
>>
>> I'm assuming I am getting the error because of something wrong with my S3
>> settings but I don't know what it would be. I'm making this assumption
>> because the /_all returns data (but I guess that could be wrong). Any
>> ideas on what the issue might be? What exactly causes
>> RepositoryMissingException?
>>
>> Thanks.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/ac375bf8-6f78-41a2-9cb0-0409234a004f%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/ac375bf8-6f78-41a2-9cb0-0409234a004f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/elasticsearch/-av1rGK1bQE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/36BC1F5F-1D3A-4E56-A519-C1952C9C0D80%40pilato.fr
>>
>> <https://groups.google.com/d/msgid/elasticsearch/36BC1F5F-1D3A-4E56-A519-C1952C9C0D80%40pilato.fr?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/c8375d28-016e-4efb-9bcb-3ece6110f053%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
