# Elasticsearch Log directory permission overriding with setgid

**URL:** <https://discuss.elastic.co/t/elasticsearch-log-directory-permission-overriding-with-setgid/178635>\
**Category:** Elasticsearch\
**Created:** [April 26, 2019, 11:35am UTC](https://discuss.elastic.co/t/elasticsearch-log-directory-permission-overriding-with-setgid/178635 "2019-04-26T11:35:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 26, 2019, 11:35am UTC](https://discuss.elastic.co/t/elasticsearch-log-directory-permission-overriding-with-setgid/178635/1 "2019-04-26T11:35:38Z")

</div>

Elasticsearch Log directory permission overriding with setgid as given

```
**[root@abcabc ~]# ll /var/log/ | grep elasticsearch**
 **drwxr-s--- 2 elasticsearch elasticsearch 4096 Apr 22 10:07 elasticsearch**

```

Due to this read-only users are facing issues in reading the logs. I have to manually reset this at the time user face the issue. But I don't know what is reasonable for this & how actually permissions are overridden.

---

<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:** [May 24, 2019, 11:49am UTC](https://discuss.elastic.co/t/elasticsearch-log-directory-permission-overriding-with-setgid/178635/2 "2019-05-24T11:49:02Z")

</div>

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