# Elasticsearch with non-root user - Backup restore is not working

**URL:** <https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177>\
**Category:** Elasticsearch\
**Tags:** docker, snapshot-and-restore\
**Created:** [November 1, 2021, 11:07pm UTC](https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177 "2021-11-01T23:07:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sagarika\_Mahalik](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@Sagarika\_Mahalik](https://discuss.elastic.co/u/Sagarika_Mahalik)\
**Post date:** [November 1, 2021, 11:07pm UTC](https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177/1 "2021-11-01T23:07:04Z")

</div>

We have a docker image for Elasticsearch where I added. a non-root user as it is required to fix some vulnerabilities. After adding non-root user, we are facing with the backup-restore functionalities. I am getting error like this in master node:  
on the first line this error:

```auto
crond: can't open or create path/crond.pid: Permission denied
these exceptions:
org.elasticsearch.transport.RemoteTransportException: [mnjdjellxxx][xxxxxx][cluster:admin/repository/put]

Caused by: org.elasticsearch.repositories.RepositoryVerificationException: [indexid] path [instances/id/] is not accessible on master node
at org.elasticsearch.repositories.blobstore.BlobStoreRepository.startVerification(BlobStoreRepository.java:1276) ~[elasticsearch-7.10.0.jar:7.10.0]

Caused by: java.io.IOException: Unable to upload object [instances/id/file.dat] using a single upload

at org.elasticsearch.repositories.s3.S3BlobContainer.executeSingleUpload(S3BlobContainer.java:360) ~[?:?]

Caused by: org.elasticsearch.common.io.stream.NotSerializableExceptionWrapper: amazon_s3_exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: xxxxxxxxxxx; S3 Extended Request ID:xcxxxxxxxxxxxxx)

at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1799) ~[?:?]

```

version: 7.10.0  
the cluster is not able to verify the snapshot repository

We are able to add data and update data to document. but not able to restore it due to this above issue.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 1, 2021, 11:52pm UTC](https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177/2 "2021-11-01T23:52:52Z")

</div>

Please format your code/logs/config using the `</>` button, or markdown style back ticks. It helps to make things easy to read which helps us help you 🙂

> [@Sagarika\_Mahalik](#):
>
> 'crond: can't open or create path/crond.pid: Permission denied

That doesn't look like an Elasticsearch error.

> [@Sagarika\_Mahalik](#):
>
> 403; Error Code: AccessDenied

Can you share your config as well as the snapshot and restore commands you are running?

---

<div class="post-metadata">

**Author:** ![Sagarika\_Mahalik](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@Sagarika\_Mahalik](https://discuss.elastic.co/u/Sagarika_Mahalik)\
**Post date:** [November 24, 2021, 7:46pm UTC](https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177/3 "2021-11-24T19:46:32Z")

</div>

This issue got fixed. Due to lack of permission, we were not able fix the issue.

---

<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:** [December 22, 2021, 7:46pm UTC](https://discuss.elastic.co/t/elasticsearch-with-non-root-user-backup-restore-is-not-working/288177/4 "2021-12-22T19:46:56Z")

</div>

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