# Azure repository snapshot error

**URL:** <https://discuss.elastic.co/t/azure-repository-snapshot-error/108379>\
**Category:** Elasticsearch\
**Created:** [November 20, 2017, 12:06pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379 "2017-11-20T12:06:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [November 20, 2017, 12:06pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379/1 "2017-11-20T12:06:39Z")

</div>

Hi,

We're using the Azure plugin for backup.  
In general it works good, but every once in a while we're seeing this error:

```auto
IndexShardSnapshotFailedException[java.lang.RuntimeException: java.security.AccessControlException: access denied (\"java.net.SocketPermission\" \"mycustomstorage.blob.core.windows.net:443\" \"connect,resolve\")]; nested: RuntimeException[java.security.AccessControlException: access denied (\"java.net.SocketPermission\" \"mycustomstorage.blob.core.windows.net:443\" \"connect,resolve\")]; nested: AccessControlException[access denied (\"java.net.SocketPermission\" \"mycustomstorage.blob.core.windows.net:443\" \"connect,resolve\")];

```

On some of the shards in a snapshot.  
Running the backup again works, but I would like to get it working on the first run.

Any idea how to approach this?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [December 8, 2017, 10:52pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379/2 "2017-12-08T22:52:30Z")

</div>

This is strange. But I suspect something wrong on azure side.

May be that on azure we should retry before failing though? @Igor_Motov thoughts?

---

<div class="post-metadata">

**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\
**Post date:** [December 9, 2017, 9:41pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379/3 "2017-12-09T21:41:08Z")

</div>

I have never seen this one. I would love to know more: elasticsearch, JVM and OS versions, stack trace, how elasticsearch was installed, etc.

---

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [December 13, 2017, 2:36pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379/4 "2017-12-13T14:36:55Z")

</div>

I just rechecked and the last time we got this error was the 26/11, and we are backing up on an hourly basis, so I guess its gone now.

I'll update this ticket if I see it again.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 10, 2018, 2:36pm UTC](https://discuss.elastic.co/t/azure-repository-snapshot-error/108379/5 "2018-01-10T14:36:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.