# Logstash loses tranmission with Filebeat

**URL:** <https://discuss.elastic.co/t/logstash-loses-tranmission-with-filebeat/125943>\
**Category:** Logstash\
**Created:** [March 28, 2018, 1:20pm UTC](https://discuss.elastic.co/t/logstash-loses-tranmission-with-filebeat/125943 "2018-03-28T13:20:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![omnitech](https://avatars.discourse-cdn.com/v4/letter/o/82dd89/32.png) [@omnitech](https://discuss.elastic.co/u/omnitech)\
**Post date:** [March 28, 2018, 1:20pm UTC](https://discuss.elastic.co/t/logstash-loses-tranmission-with-filebeat/125943/1 "2018-03-28T13:20:26Z")

</div>

Hi,

I am currently using Logstash and Filebeat for our central log server and for some reason it loses a sync about every two weeks. Both servers are currently running Ubuntu 16.04, and Logstash and Filebeat are version 5.6.7. There are no issues such as power outages or network downtime that I am aware when it is happening.

Using tail for both services show that they are trying to send each other information, but they are out of sync. As a temporary solution I just restart the Logstash service and everything is in sync again for about two until the same issue happens. Restarting the Filebeat service instead does not sync the connection, so I assume it is an issue with Logtstash.

Is this a known issue with version 5.6.7 losing sync over time? If there is not a solution/answer, is there a way to make the Logstash service automatically restart if the connection is down for a certain period of time?

Thank you,

Josh

---

<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 25, 2018, 1:20pm UTC](https://discuss.elastic.co/t/logstash-loses-tranmission-with-filebeat/125943/2 "2018-04-25T13:20:28Z")

</div>

Closed on April 25, 2018, 1:20pm UTC

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