# Filebeat might erroneously hold on to the file descriptor?

**URL:** https://discuss.elastic.co/t/filebeat-might-erroneously-hold-on-to-the-file-descriptor/104957
**Category:** Beats
**Tags:** filebeat
**Created:** [October 23, 2017, 7:18pm UTC](https://discuss.elastic.co/t/filebeat-might-erroneously-hold-on-to-the-file-descriptor/104957 "2017-10-23T19:18:53Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![vkakhnych](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vkakhnych/32/23344_2.png) [@vkakhnych](https://discuss.elastic.co/u/vkakhnych)
#### Post date: [October 24, 2017, 12:44pm UTC](https://discuss.elastic.co/t/filebeat-might-erroneously-hold-on-to-the-file-descriptor/104957/2 "2017-10-24T12:44:28Z")

</div>

> [@Filebeat is not closig the file descriptor once the file is deleted/renamed](https://discuss.elastic.co/t/filebeat-is-not-closig-the-file-descriptor-once-the-file-is-deleted-renamed/104077/10):
>
> Have the same issue. Old logs are rename each hour, then delete after hour of inactivity by script. But filebeat still keep all or many of them open. Can't reproduce in test lab, only on prod get it. Maybe it's related to intensive of logging. Config: filebeat.prospectors: - input\_type: log paths: - /var/log/batch/Batch\*-running.log close\_inactive: 5m close\_renamed: true clean\_removed: true close\_removed is enabled by default (according to official documentation) filebeat-5.6.…

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-might-erroneously-hold-on-to-the-file-descriptor/104957)._