@dwradcliffe There are some edge cases where it can happen that in 1.2.3 file handlers are leaked. All these edge cases should be resolved in the 5.0 releases. Could you test the 5.0.0-alpha5 release or nightly build (https://beats-nightlies.s3.amazonaws.com/index.html?prefix=filebeat/) to see if you still have the issue? To know more about your case, I would also need config file and some log outputs. Please open a new topic for this.
I would like to join the discussion. I'm following and applying changes in this forum the past week.
Sadly I still experience the problem:
filebeat 31 root 1r REG 253,16 10486094 4751403 /opt/xxx/logs/supervisor.out.log.10 (deleted)
.
.
.
Currently I'm running filebeat version 6.0.0-alpha1 with following configuration:
paths:
- /opt/xxx/logs/*.log
close_older: 1m
ignore_older: 1m
scan_frequency: 10s
force_close_files: true
I appreciate any input to solve the problem.
@ronny.lerch Can you open a new discuss topic with this as this one is already marked as resovled. Can you share there your full config and if possible some log files from filebeat?