# Beats Input Plugin stops when Go client killed

**URL:** <https://discuss.elastic.co/t/beats-input-plugin-stops-when-go-client-killed/58537>\
**Category:** Logstash\
**Created:** [August 21, 2016, 7:31pm UTC](https://discuss.elastic.co/t/beats-input-plugin-stops-when-go-client-killed/58537 "2016-08-21T19:31:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![FredPlex](https://avatars.discourse-cdn.com/v4/letter/f/77aa72/32.png) [@FredPlex](https://discuss.elastic.co/u/FredPlex)\
**Post date:** [August 21, 2016, 7:31pm UTC](https://discuss.elastic.co/t/beats-input-plugin-stops-when-go-client-killed/58537/1 "2016-08-21T19:31:25Z")

</div>

Hey folks...

We have written a Go client that streams records to logstash the setup is as such:

Go client written in go using [https://github.com/elastic/go-lumber](https://github.com/elastic/go-lumber) sending records to logstash:5044

logstash 2.3.4 with logstash-input-beats (2.2.9) listening on 5044:

input config:  
beats {  
port =\> 5044  
type =\> "my\_platform"  
codec =\> {charset =\> "UTF-8" }  
}  
}

things work great but if the go client is killed (ctrl-c in foreground) or kill -9 or abruptly crashes, the beats-plugin goes away and port 5044 is not listening any longer - interesting there are no messages in the logstash.log about this, no exceptions etc...

...any thoughts on this?

I tried to updated the beats plugin to 3.0.4 but it sits there forever trying to update CPU spins but nothing happens.

not sure what to do next here.

thx, FredPlex

---

<div class="post-metadata">

**Author:** ![FredPlex](https://avatars.discourse-cdn.com/v4/letter/f/77aa72/32.png) [@FredPlex](https://discuss.elastic.co/u/FredPlex)\
**Post date:** [August 21, 2016, 9:24pm UTC](https://discuss.elastic.co/t/beats-input-plugin-stops-when-go-client-killed/58537/2 "2016-08-21T21:24:25Z")

</div>

more details... I must have missed it earlier but in the log stash stderr I see this when the issue happens:

NoMethodError: undefined method `flush' for ["charset", "UTF-8"]:Array  
flush at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-beats-2.2.9/lib/logstash/inputs/beats\_support/connection\_handler.rb:81  
handle\_new\_connection at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-beats-2.2.9/lib/logstash/inputs/beats.rb:229  
run at /opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-beats-2.2.9/lib/logstash/inputs/beats.rb:167

---

<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:** [July 6, 2017, 4:42am UTC](https://discuss.elastic.co/t/beats-input-plugin-stops-when-go-client-killed/58537/3 "2017-07-06T04:42:25Z")

</div>