# Filebeat to Logstash - "client is not connected"

**URL:** <https://discuss.elastic.co/t/filebeat-to-logstash-client-is-not-connected/116932>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 24, 2018, 10:03pm UTC](https://discuss.elastic.co/t/filebeat-to-logstash-client-is-not-connected/116932 "2018-01-24T22:03:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [January 25, 2018, 8:17pm UTC](https://discuss.elastic.co/t/filebeat-to-logstash-client-is-not-connected/116932/6 "2018-01-25T20:17:07Z")

</div>

With the client inactivity timeout increased LS shouldn't be disconnecting the clients. Back-pressure from ES shouldn't cause disconnection either.

If you run logstash with trace logging enabled this might help figure out why the client is disconnecting (`--log.level trace`).

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-to-logstash-client-is-not-connected/116932)._