# Filebeat 5.3.1 config\_dir files needs 644 permissions?

**URL:** <https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 30, 2017, 8:49am UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108 "2017-04-30T08:49:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefanrinderle](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@stefanrinderle](https://discuss.elastic.co/u/stefanrinderle)\
**Post date:** [April 30, 2017, 8:49am UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/1 "2017-04-30T08:49:26Z")

</div>

Hi,

i just spend a few ours on this topic. As far as i can see now, filebeat ignores files placed in the config\_dir folder with 664 permission without any comment in the log file. Changing the permissions to 644 and restart filebeat works.

Is this a bug or a feature? Is there any way to disable the permission check?

Thanks in advance

Stefan

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 2, 2017, 1:47pm UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/2 "2017-05-02T13:47:34Z")

</div>

There's a [section](https://www.elastic.co/guide/en/beats/libbeat/5.3/config-file-permissions.html) on this in the docs. We should link to it from the config reload docs.

---

<div class="post-metadata">

**Author:** ![stefanrinderle](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@stefanrinderle](https://discuss.elastic.co/u/stefanrinderle)\
**Post date:** [May 2, 2017, 2:06pm UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/3 "2017-05-02T14:06:25Z")

</div>

Yeah, thanks. That looks nice. It would be great to link that.

Unfortunately, there is no "Exiting: error loading config file" if the file permissions of the config files referenced in the "config\_dir" folder have ther permission 664. The documentation only refers to the "master" config file.

It would be great if there would be also an exception in this case, or?

Thanks,  
Stefan

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 3, 2017, 4:12am UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/4 "2017-05-03T04:12:17Z")

</div>

Yeah, I would expect a warning or error in the log file when the dynamic config file is ignored due to permissions issue. If there's no error message then that's a bug.

Can you check if you see this error in your logs: [https://github.com/elastic/beats/blob/v5.3.1/libbeat/cfgfile/reload.go#L117](https://github.com/elastic/beats/blob/v5.3.1/libbeat/cfgfile/reload.go#L117)

Also can you open a Github issue about linking to the _Config File Ownership and Permissions_ page.

---

<div class="post-metadata">

**Author:** ![stefanrinderle](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@stefanrinderle](https://discuss.elastic.co/u/stefanrinderle)\
**Post date:** [May 3, 2017, 1:06pm UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/5 "2017-05-03T13:06:50Z")

</div>

Created an issue as there is nothing in the log:

> <https://github.com/elastic/beats/issues/4187>

Cheers,  
Stefan

---

<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 21, 2017, 8:57am UTC](https://discuss.elastic.co/t/filebeat-5-3-1-config-dir-files-needs-644-permissions/84108/6 "2017-05-21T08:57:48Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
