# Intermittent connectivity issues between Filebeat and Logstash

**URL:** <https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [January 23, 2020, 3:53pm UTC](https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286 "2020-01-23T15:53:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sagar\_Kalburgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sagar_kalburgi/32/61300_2.png) [@Sagar\_Kalburgi](https://discuss.elastic.co/u/Sagar_Kalburgi)\
**Post date:** [January 23, 2020, 3:53pm UTC](https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286/1 "2020-01-23T15:53:16Z")

</div>

I have few Filebeat containers and a single logstash container running on a paticular namespaces of a kubernetes cluster.

However, I see intermittent connectivity issues between Filebeat and Logstash. (Logs below)  
Due to this I see that Filebeat repeatedly sends the same events to Logstash.

\<\>|2020-01-23T15:43:14.925Z|ERROR|logstash/sync.go:155|Failed to publish events caused by: read tcp 100.96.10.3:59614-\>100.68.143.9:5044: i/o timeout|  
|---|---|---|---|  
|2020-01-23T15:43:16.813Z|ERROR|pipeline/output.go:121|Failed to publish events: read tcp 100.96.10.3:59614-\>100.68.143.9:5044: i/o timeout|  
|2020-01-23T15:43:16.814Z|INFO|pipeline/output.go:95|Connecting to backoff(tcp://local-logstash:5044)|  
|2020-01-23T15:43:16.818Z|INFO|pipeline/output.go:105|Connection to backoff(tcp://local-logstash:5044) established|\</\>

---

<div class="post-metadata">

**Author:** ![Loran\_Fininure](https://avatars.discourse-cdn.com/v4/letter/l/4da419/32.png) [@Loran\_Fininure](https://discuss.elastic.co/u/Loran_Fininure)\
**Post date:** [January 26, 2020, 6:20am UTC](https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286/2 "2020-01-26T06:20:26Z")

</div>

I have the same issue. Im running both Logstash and Filebeat 7.5.2 on Docker. Both containers are in the same docker-network on the same host. Moving the Filebeat out of Docker onto the host has the same issue. Recreating the containers+networks or restarting the Docker-daemon does not solve the problem either.  
Filebeat manages to write events to Logstash, but is reconnecting every 60s due to this i/o timeout error.  
As far as I can tell, there is no networking issue between these containers. Ping, telnet and curl do work flawlessly.

Edit: Using Filebeat and Logstash Image 7.5.1 does not have that issue in the very same setup.

---

<div class="post-metadata">

**Author:** ![Sagar\_Kalburgi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sagar_kalburgi/32/61300_2.png) [@Sagar\_Kalburgi](https://discuss.elastic.co/u/Sagar_Kalburgi)\
**Post date:** [January 26, 2020, 11:58pm UTC](https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286/3 "2020-01-26T23:58:51Z")

</div>

Btw, I'm also able to telnet into logstash port from filebeat container

---

<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:** [February 24, 2020, 12:10am UTC](https://discuss.elastic.co/t/intermittent-connectivity-issues-between-filebeat-and-logstash/216286/4 "2020-02-24T00:10:58Z")

</div>

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