# Logstash crash / failed to connect to es cluster

**URL:** <https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268>\
**Category:** Logstash\
**Created:** [October 15, 2015, 1:03pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268 "2015-10-15T13:03:49Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 15, 2015, 1:03pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/1 "2015-10-15T13:03:49Z")

</div>

I have an Issue that when i killed logstash and runned it again it it should pass 5k of messages and it does not. There are two errors there

One about no nodes avaible  
Second :message=\>"Got error to send bulk of actions: Failed to deserialize exception response from stream", :level=\>:error}

Got logstash 1.5.4 with cluster of es on version 1.7.2  
I use transport protocol for it.

Any help would be nice.

---

<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:** [October 15, 2015, 1:29pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/2 "2015-10-15T13:29:17Z")

</div>

I'd recommend switching to the HTTP protocol. Doing so will almost certainly resolve this problem.

---

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 15, 2015, 1:47pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/3 "2015-10-15T13:47:23Z")

</div>

That is not an solution.  
The problem exist somewhere and i need to fix it.  
And if it is not my fault it needs to be fixed for future users

---

<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:** [October 15, 2015, 1:54pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/4 "2015-10-15T13:54:09Z")

</div>

Of course it's a solution, just not the solution you like.

To increase your chances of getting a solution you _do_ like, please quote complete error messages instead of saying e.g. "one about no nodes available".

---

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 15, 2015, 2:04pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/5 "2015-10-15T14:04:11Z")

</div>

One :

```
{:timestamp=>"2015-10-15T14:25:28.563000+0200", :message=>"Got error to send bulk of actions: None of the configured nodes are available: []", :level=>:error}
{:timestamp=>"2015-10-15T14:25:28.865000+0200", :message=>"Failed to flush outgoing items", :outgoing_count=>1, :exception=>"Java::OrgElasticsearchClientTransport::NoNodeAvailableException", :backtrace=>["org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(org/elasticsearch/client/transport/TransportClientNodesService.java:279)",

```

Second:

```
:timestamp=>"2015-10-15T14:25:18.658000+0200", :message=>"Got error to send bulk of actions: Failed to deserialize exception response from stream", :level=>:error}
```

---

<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:** [October 15, 2015, 2:07pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/6 "2015-10-15T14:07:23Z")

</div>

And how's the health of the cluster? What does Logstash's elasticsearch output configuration look like?

---

<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:** [October 15, 2015, 8:47pm UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/7 "2015-10-15T20:47:07Z")

</div>

As Magnus alluded, check your ES cluster. Chances are it's overloaded.

---

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 16, 2015, 8:23am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/8 "2015-10-16T08:23:42Z")

</div>

I checked the cluster and it is green. Its not about overload either since it is only input ( about 1k messages )

Config

output {  
elasticsearch{  
host =\> ["xxx.xxx.xxxx.xxx:9300","xxx.xxx.xxxx.xxx:9301","xxx.xxx.xxxx.xxx:9302"]  
action =\> "index"  
cluster =\> "elasticsearch"  
index =\> "sergiusz"  
protocol =\> "transport"  
port =\> "9300-9305"  
}

}

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 16, 2015, 8:34am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/9 "2015-10-16T08:34:12Z")

</div>

Is Logstash and Elasticsearch running the same Java version? If this is not the case it can cause problems, which is why HTTP will be the default protocol used by Logstash from version 2.0.

---

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 16, 2015, 8:35am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/10 "2015-10-16T08:35:06Z")

</div>

they run on same machine so Yes its same java i have readed about that already before i asked the question.

---

<div class="post-metadata">

**Author:** ![quejinho](https://avatars.discourse-cdn.com/v4/letter/q/3bc359/32.png) [@quejinho](https://discuss.elastic.co/u/quejinho)\
**Post date:** [October 16, 2015, 9:12am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/11 "2015-10-16T09:12:52Z")

</div>

As i found out there was some error in different logstash . Did not saw that . All works now.

---

<div class="post-metadata">

**Author:** ![James\_Tang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_tang/32/8112_2.png) [@James\_Tang](https://discuss.elastic.co/u/James_Tang)\
**Post date:** [October 21, 2015, 2:58am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/12 "2015-10-21T02:58:27Z")

</div>

Is it possible to reveal the issue faced? I am facing similar issue and I am trying to eliminate the possibilities so as to identify the root cause.

regards

---

<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:25am UTC](https://discuss.elastic.co/t/logstash-crash-failed-to-connect-to-es-cluster/32268/13 "2017-07-06T05:25:58Z")

</div>


