# Logstash crashing

**URL:** <https://discuss.elastic.co/t/logstash-crashing/69408>\
**Category:** Logstash\
**Created:** [December 19, 2016, 8:59am UTC](https://discuss.elastic.co/t/logstash-crashing/69408 "2016-12-19T08:59:35Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 8:59am UTC](https://discuss.elastic.co/t/logstash-crashing/69408/1 "2016-12-19T08:59:35Z")

</div>

Hi,

I have regulary my logstash server crashing.

Sometimes after a few restart it works again but alwais crash after a fex hours.

As i'm not a king in linux/logstash can you help me to find out what's wrong ?

Here is the logstas.log:

> {:timestamp=\>"2016-12-19T09:54:28.139000+0100", :message=\>"Could not start TCP server: Address in use", :host=\>"0.0.0.0", :port=\>1514, :level=\>:error}  
> {:timestamp=\>"2016-12-19T09:54:28.169000+0100", :message=\>"An unexpected error occurred!", :error=\>#\<Errno::EADDRINUSE: Address already in use - bind - Address already in use\>, :class=\>"Errno::EADDRINUSE", :backtrace=\>["org/jruby/ext/socket/RubyTCPServer.java:118:in `initialize'", "org/jruby/RubyIO.java:853:in `new'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-3.0.4/lib/logstash/inputs/tcp.rb:244:in `new_server_socket'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-input-tcp-3.0.4/lib/logstash/inputs/tcp.rb:79:in `register'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:322:in `start_inputs'", "org/jruby/RubyArray.java:1613:in `each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:321:in `start_inputs'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:172:in `start\_workers'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/pipeline.rb:126:in `run'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/agent.rb:210:in `execute'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/runner.rb:90:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.4-java/lib/logstash/runner.rb:95:in `run'", "org/jruby/RubyProc.java:281:in `call'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/task.rb:24:in `initialize'"], :level=\>:warn}  
> ~

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [December 19, 2016, 9:17am UTC](https://discuss.elastic.co/t/logstash-crashing/69408/2 "2016-12-19T09:17:50Z")

</div>

Is another process listening on port 1514? Do you have multiple tcp inputs listing the same port somewhere in /etc/logstash/conf.d?

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 10:34am UTC](https://discuss.elastic.co/t/logstash-crashing/69408/3 "2016-12-19T10:34:09Z")

</div>

in /etc/logstash/conf.d i have only one listening on 1514.

How can i check if another process is listening that port ?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [December 19, 2016, 10:42am UTC](https://discuss.elastic.co/t/logstash-crashing/69408/4 "2016-12-19T10:42:23Z")

</div>

> How can i check if another process is listening that port ?

Use netstat or lsof.

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 4:02pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/5 "2016-12-19T16:02:16Z")

</div>

I've chec and i can't see any other app using port 1514

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 4:09pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/6 "2016-12-19T16:09:31Z")

</div>

Actually the service is up again, but i can't see data in kibana.

I don't know if it can't receive it or if it didn't parse it.

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 4:15pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/7 "2016-12-19T16:15:39Z")

</div>

Actually the service is up again, but i can't see data in kibana.

I don't know if it can't receive it or if it didn't parse it.

I just start it in debug:

> Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory  
> 3071  
> Try using the -Djava.io.tmpdir= option to select an alternate temp location.

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 4:28pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/8 "2016-12-19T16:28:33Z")

</div>

Something looks to be connected but i have no idea what it is ...

> tcp6 218 0 10.9.8.218:1514 184.39-65-87.adsl:59659 ESTABLISHED  
> tcp6 113 0 10.9.8.218:1514 184.39-65-87.adsl:65035 ESTABLISHED  
> tcp6 0 0 10.9.8.218:1514 184.39-65-87.adsl:65248 ESTABLISHED  
> tcp6 452 0 10.9.8.218:1514 184.39-65-87.adsl:55448 ESTABLISHED

---

<div class="post-metadata">

**Author:** ![Karl\_Trasschaert](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@Karl\_Trasschaert](https://discuss.elastic.co/u/Karl_Trasschaert)\
**Post date:** [December 19, 2016, 4:34pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/9 "2016-12-19T16:34:46Z")

</div>

Maybe a space issue ??

> E: You don't have enough free space in /var/cache/apt/archives/.

Can i delete logs ? where are they stored ?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [December 19, 2016, 5:57pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/10 "2016-12-19T17:57:22Z")

</div>

> Can i delete logs ? where are they stored ?

Use the Elasticsearch REST APIs to delete indexes.

---

<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:** [January 16, 2017, 5:57pm UTC](https://discuss.elastic.co/t/logstash-crashing/69408/11 "2017-01-16T17:57:26Z")

</div>

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