# Filbeat process fails after SAN controller restart

**URL:** <https://discuss.elastic.co/t/filbeat-process-fails-after-san-controller-restart/124970>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 21, 2018, 11:27am UTC](https://discuss.elastic.co/t/filbeat-process-fails-after-san-controller-restart/124970 "2018-03-21T11:27:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![playfair039](https://avatars.discourse-cdn.com/v4/letter/p/94ad74/32.png) [@playfair039](https://discuss.elastic.co/u/playfair039)\
**Post date:** [March 21, 2018, 11:27am UTC](https://discuss.elastic.co/t/filbeat-process-fails-after-san-controller-restart/124970/1 "2018-03-21T11:27:01Z")

</div>

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:  
Uptime: 16.306867ms  
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](https://github.com/elastic/beats/issues/3537) so the question: What version of filebeat fixes this?

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [March 22, 2018, 1:59pm UTC](https://discuss.elastic.co/t/filbeat-process-fails-after-san-controller-restart/124970/2 "2018-03-22T13:59:47Z")

</div>

It seems as mentioned in the last comment we only applied it to winlogbeat and not filebeat yet ☹ [https://github.com/elastic/beats/issues/3537#issuecomment-372114774](https://github.com/elastic/beats/issues/3537#issuecomment-372114774) So this is still open.

---

<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:** [April 19, 2018, 1:59pm UTC](https://discuss.elastic.co/t/filbeat-process-fails-after-san-controller-restart/124970/3 "2018-04-19T13:59:58Z")

</div>

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