# LS forwarder erroring out on the LS server

**URL:** <https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740>\
**Category:** Logstash\
**Created:** [July 16, 2015, 6:24pm UTC](https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740 "2015-07-16T18:24:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [July 16, 2015, 6:24pm UTC](https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740/1 "2015-07-16T18:24:16Z")

</div>

Hey guys,

We have logstash forwarder setup on a bunch of nodes. And initially we had results turn up in the logstash interface when you did a search.

However the servers that were running forwarder stopped turning up in results in the kibana - logstash interface, and, and we started seeing these errors turn up in the logstash logs:

```
{:timestamp=>"2015-07-16T14:15:19.148000-0400", :message=>"An error occurred. Closing connection", :client=>"3.3.81.28:41584", :exception=>#<LogStash::ShutdownSignal: LogStash::ShutdownSignal>, :backtrace=>["org/jruby/RubyIO.java:2996:in `sysread'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:164:in `read'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:112:in `handle_socket'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:147:in `client_thread'"], :level=>:error}
{:timestamp=>"2015-07-16T14:15:19.148000-0400", :message=>"An error occurred. Closing connection", :client=>"3.3.81.115:45836", :exception=>#<LogStash::ShutdownSignal: LogStash::ShutdownSignal>, :backtrace=>["org/jruby/RubyIO.java:2996:in `sysread'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:164:in `read'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:112:in `handle_socket'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-0.1.5/lib/logstash/inputs/tcp.rb:147:in `client_thread'"], :level=>:error}

```

Does this provide any clues on how to solve this problem? Are there any troubleshooting steps you can recommend?

Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 18, 2015, 4:16am UTC](https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740/2 "2015-07-18T04:16:18Z")

</div>

Looks like it received a shutdown signal from somewhere?  
Anything in your OS logs showing this?

---

<div class="post-metadata">

**Author:** ![bluethundr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bluethundr/32/409_2.png) [@bluethundr](https://discuss.elastic.co/u/bluethundr)\
**Post date:** [July 30, 2015, 3:55pm UTC](https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740/3 "2015-07-30T15:55:54Z")

</div>

Hey Warkolm,

Sorry for the delayed response. I've been on vacation for a week and then just been busy.

But it's been a while since we've sen this issue. It hasn't happened since. I'll let you know if we have it again.

Thanks,

Tim

---

<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, 5:33am UTC](https://discuss.elastic.co/t/ls-forwarder-erroring-out-on-the-ls-server/25740/4 "2017-07-06T05:33:19Z")

</div>