# Filebeat-6.5.1 Registry is Never Cleaned

**URL:** <https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 14, 2018, 7:47am UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861 "2018-12-14T07:47:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![396175371](https://avatars.discourse-cdn.com/v4/letter/3/7ab992/32.png) [@396175371](https://discuss.elastic.co/u/396175371)\
**Post date:** [December 14, 2018, 7:47am UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861/1 "2018-12-14T07:47:55Z")

</div>

Filebeat 6.5.1, Red Hat 4.4.7  
my filebeat can not clean up registry,

Here is the my config:

```
filebeat.inputs:
- type: log
  enabled: true
  paths:
    - /vol/*.log
  encoding: utf-8
  exclude_files: ['.*gc.log$']
  multiline.pattern: ^[0-9]{10}\.[0-9]{3}[[:space:]]\[
  multiline.negate: true
  multiline.match: after
  multiline.timeout: 8s
  backoff: 2s
  max_backoff: 10s
  backoff_factor: 3
  close_inactive: 5m
  clean_inactive: 3h
  scan_frequency: 10s
  ignore_older: 2h
  close_removed: true
  clean_removed: true
  harvester_buffer_size: 16384
  max_bytes: 1485760
filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: false

setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression
  _source.enabled: true

name: test
queue:
  mem:
    events: 4096 
    flush.min_events: 2048
    flush.timeout: 10s
max_procs: 1
setup.kibana:
setup.template.name: "test"
setup.template.pattern: "test-*"
output.elasticsearch:
  hosts: ["localhost:9200"]
  pipeline: "test-pipeline"
  index: "sms-%{+yyyy.MM.dd}"
processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - drop_fields:
     fields: ["_type","_score","beat.version","host","prospector"]
logging.metrics.enabled: true
logging.metrics.period: 5m
logging.to_files: true
logging.files:
  path: 
  name: filebeat.log
  rotateeverybytes: 10485760 
  keepfiles: 7
  permissions: 0644

  redirect_stderr: true

```

pls help

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [December 17, 2018, 3:45pm UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861/2 "2018-12-17T15:45:19Z")

</div>

Hello @396175371, Are you talking about Filebeat's own registry? It should be cleaned periodically and running filebeat with logging in debug mode should display a statement about cleaning states.

---

<div class="post-metadata">

**Author:** ![396175371](https://avatars.discourse-cdn.com/v4/letter/3/7ab992/32.png) [@396175371](https://discuss.elastic.co/u/396175371)\
**Post date:** [December 21, 2018, 8:29am UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861/3 "2018-12-21T08:29:27Z")

</div>

I want to know if the filebeat registration file still saves this information when the filebeat has no log output and exceeds the clean\_inactive configuration time. Is it supposed to be empty after the clean\_inactive time?

---

<div class="post-metadata">

**Author:** ![396175371](https://avatars.discourse-cdn.com/v4/letter/3/7ab992/32.png) [@396175371](https://discuss.elastic.co/u/396175371)\
**Post date:** [December 21, 2018, 8:31am UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861/4 "2018-12-21T08:31:52Z")

</div>

Exceeded the time of the clean\_inactive configuration, why the contents of the registration file have not been emptied yet?

---

<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:** [January 18, 2019, 8:34am UTC](https://discuss.elastic.co/t/filebeat-6-5-1-registry-is-never-cleaned/160861/5 "2019-01-18T08:34:18Z")

</div>

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