I've had a few issues with filebeat in my reference environment where after restarting the SAN controller as part of tests, the filebeat process stops and fails to restart - fixed by restarting after removing the registry file in /var/lib/filebeat/registry (Red Hat Enterprise Linux Server release 7.4 (Maipo)).
Filebeat logs look something like this:
INFO Flush Interval set to: 1s
Max Bulk Size set to: 50
filebeat start running.
Registry file set to: /var/lib/filebeat/registry
Loading registrar data from /var/lib/filebeat/registry
Total non-zero values:
INFO filebeat stopped.
CRIT Exiting: Could not start registrar: Error loading state: Error decoding states: EOF
I'm fairly familiar with https://github.com/elastic/beats/issues/3537 so the question: What version of filebeat fixes this?