# About clean\_removed in Filebeat 5.0.0-alpha5 **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [September 7, 2016, 8:34am UTC](https://discuss.elastic.co/t/about-clean-removed-in-filebeat-5-0-0-alpha5/59949 "2016-09-07T08:34:35Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![vin](https://avatars.discourse-cdn.com/v4/letter/v/a87d85/32.png) [@vin](https://discuss.elastic.co/u/vin)\ **Post date:** [September 7, 2016, 9:57am UTC](https://discuss.elastic.co/t/about-clean-removed-in-filebeat-5-0-0-alpha5/59949/2 "2016-09-07T09:57:50Z")
About this ERR log: > 2016-09-07T20:25:40+08:00 ERR File is falling under ignore\_older before harvesting is finished. Adjust your close\_\* settings I got your explain at [Filebeat Stop Cleaning Registry - #8 by Gabry993](https://discuss.elastic.co/t/filebeat-stop-cleaning-registry/58902/8) : > The first error is shown, in case a file did not finish harvesting yet but already falls under ignore\_older. This can for example happen when a file is not updated anymore, but the harvester can't finish reading it as the output is not available or too slow. As soon as the output catches up, the file will be closed and ignored. But in my case, the ERR log is appeared when start filebeat, the file should not begin harvesting, not "in case a file did not finish harvesting yet " . --- _[View the full topic](https://discuss.elastic.co/t/about-clean-removed-in-filebeat-5-0-0-alpha5/59949)._