# Filebeat : Badly Stuck with Connection reset by peer error **URL:** https://discuss.elastic.co/t/filebeat-badly-stuck-with-connection-reset-by-peer-error/66878 **Category:** Beats **Tags:** filebeat **Created:** [November 22, 2016, 3:16pm UTC](https://discuss.elastic.co/t/filebeat-badly-stuck-with-connection-reset-by-peer-error/66878 "2016-11-22T15:16:48Z") **Posts on this page:** 1 **Showing post:** 11
### Author: ![jashwanth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jashwanth/32/100451_2.png) [@jashwanth](https://discuss.elastic.co/u/jashwanth) #### Post date: [November 22, 2016, 6:34pm UTC](https://discuss.elastic.co/t/filebeat-badly-stuck-with-connection-reset-by-peer-error/66878/11 "2016-11-22T18:34:52Z")
As per @tomwj post [Elasitcsearch-ruby raises "Cannot get new connection from pool" error](https://discuss.elastic.co/t/elasitcsearch-ruby-raises-cannot-get-new-connection-from-pool-error/36252/12) I tried by removing sniffing =\> true. I'm able to insert data to elastic search by using nc command through tcp 5044 port with below config. [ec2-user@ip-10-3-1-13 conf.d]$ nc elk\_server\_ip.compute-1.amazonaws.com 5044 jashwanth dsjdskadjasdhskadf asfjkdsfhdsfkf fskjhasfkjfs asfjkfashsaf khfdslaf Config for testing: input { tcp { port =\> 5044 } } So, there is no issues with logstash and ES end now. Still able to see below error in filebeat end and suspecting the logs are not reaching logstash from filebeat. **2016-11-22T18:32:22Z DBG Try to publish 932 events to logstash with window size 1** **2016-11-22T18:32:22Z DBG close connection** **2016-11-22T18:32:22Z DBG 0 events out of 932 events sent to logstash. Continue sending ...** **2016-11-22T18:32:22Z INFO Error publishing events (retrying): EOF** **2016-11-22T18:32:22Z INFO send fail** **2016-11-22T18:32:22Z INFO backoff retry: 1m0s** --- _[View the full topic](https://discuss.elastic.co/t/filebeat-badly-stuck-with-connection-reset-by-peer-error/66878)._