# Logstash and Elastisearch doesn't communicate

**URL:** https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055
**Category:** Elasticsearch
**Created:** [February 27, 2014, 4:47pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055 "2014-02-27T16:47:11Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Hector\_Moreno\_Blanco](https://avatars.discourse-cdn.com/v4/letter/h/f08c70/32.png) [@Hector\_Moreno\_Blanco](https://discuss.elastic.co/u/Hector_Moreno_Blanco)
#### Post date: [February 27, 2014, 4:47pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/1 "2014-02-27T16:47:11Z")

</div>

Helloy everyone,

I have installed elasticsearch-1.0.1-1.noarch and  
logstash-1.3.3-flatjar.jar. I can't make logstash communicate to  
elasticsearch.

In elasticsearch.yml I have set just the cluster name (the rest is the  
default configuration). And I have this logstash.conf file (very simple):

input {  
file {  
type =\> "linux-syslog"  
path =\> ["/var/log/messages"]  
}  
}  
output {  
elasticsearch {  
embedded =\> false  
cluster =\> "my\_cluster"  
}  
}

Elasticsearch is running and for testing I execute:

java -jar /opt/logstash/logstash-1.3.3-flatjar.jar agent -f  
/opt/logstash/logstash.conf

But it doesn't work.

I can see in my\_cluster.log these errors:

[2014-02-27 17:34:34,863][WARN][discovery.zen.ping.multicast] [X-Man]  
failed to read requesting data from /192.168.13.17:54328  
java.io.IOException: No transport address mapped to [21345]  
at  
org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71)  
at  
org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267)  
at  
org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257)  
at  
org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410)  
at java.lang.Thread.run(Thread.java:744)

And in the java execution screen:

log4j, [2014-02-27T17:35:01.851] WARN: org.elasticsearch.discovery:  
[Sabreclaw] waited for 30s and no initial state was set by the discovery

I assume they are not connecting each other (nodes with different names,  
failing request, no transport...).

Any idea about what is wrong with my elasticsearch + logstash configuration?

Thank you very much in advanced.  
Kind regards.

Héctor Moreno Blanco.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![jdepp99](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jdepp99](https://discuss.elastic.co/u/jdepp99)
#### Post date: [February 27, 2014, 5:37pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/2 "2014-02-27T17:37:21Z")

</div>

I had a similar issue and the problem was the .conf file in logstash. I had to ensure tcp input type was set to codex =\> "json"

---

<div class="post-metadata">

### Author: ![Sean\_Clemmer](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Sean\_Clemmer](https://discuss.elastic.co/u/Sean_Clemmer)
#### Post date: [February 27, 2014, 6:16pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/3 "2014-02-27T18:16:37Z")

</div>

Logstash 1.3.3 is meant to work with Elasticsearch 0.90.9. See "VERSION  
NOTE" in [Elasticsearch output plugin | Logstash Reference [8.11] | Elastic](http://logstash.net/docs/1.3.3/outputs/elasticsearch)

On Thu, Feb 27, 2014 at 8:47 AM, Héctor Moreno Blanco \<  
[hector.moreno.blanco@gmail.com](mailto:hector.moreno.blanco@gmail.com)\> wrote:

> Helloy everyone,
> 
> I have installed elasticsearch-1.0.1-1.noarch and  
> logstash-1.3.3-flatjar.jar. I can't make logstash communicate to  
> elasticsearch.
> 
> In elasticsearch.yml I have set just the cluster name (the rest is the  
> default configuration). And I have this logstash.conf file (very simple):
> 
> input {  
> file {  
> type =\> "linux-syslog"  
> path =\> ["/var/log/messages"]  
> }  
> }  
> output {  
> elasticsearch {  
> embedded =\> false  
> cluster =\> "my\_cluster"  
> }  
> }
> 
> Elasticsearch is running and for testing I execute:
> 
> java -jar /opt/logstash/logstash-1.3.3-flatjar.jar agent -f  
> /opt/logstash/logstash.conf
> 
> But it doesn't work.
> 
> I can see in my\_cluster.log these errors:
> 
> [2014-02-27 17:34:34,863][WARN][discovery.zen.ping.multicast] [X-Man]  
> failed to read requesting data from /192.168.13.17:54328  
> java.io.IOException: No transport address mapped to [21345]  
> at  
> org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71)  
> at  
> org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267)  
> at  
> org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257)  
> at  
> org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410)  
> at java.lang.Thread.run(Thread.java:744)
> 
> And in the java execution screen:
> 
> log4j, [2014-02-27T17:35:01.851] WARN: org.elasticsearch.discovery:  
> [Sabreclaw] waited for 30s and no initial state was set by the discovery
> 
> I assume they are not connecting each other (nodes with different names,  
> failing request, no transport...).
> 
> Any idea about what is wrong with my elasticsearch + logstash  
> configuration?
> 
> Thank you very much in advanced.  
> Kind regards.
> 
> Héctor Moreno Blanco.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CADa-AwcCq2uJJCX7HDNyvF7Ms0AHzYGE8t6Ws-ZPpVzPdiryvA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADa-AwcCq2uJJCX7HDNyvF7Ms0AHzYGE8t6Ws-ZPpVzPdiryvA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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: [February 27, 2014, 9:33pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/4 "2014-02-27T21:33:26Z")

</div>

You're better off using the elasticsearch\_http output.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 28 February 2014 05:16, Sean Clemmer [sclemmer@bluejeansnet.com](mailto:sclemmer@bluejeansnet.com) wrote:

> Logstash 1.3.3 is meant to work with Elasticsearch 0.90.9. See "VERSION  
> NOTE" in [Elasticsearch output plugin | Logstash Reference [8.11] | Elastic](http://logstash.net/docs/1.3.3/outputs/elasticsearch)
> 
> On Thu, Feb 27, 2014 at 8:47 AM, Héctor Moreno Blanco \<  
> [hector.moreno.blanco@gmail.com](mailto:hector.moreno.blanco@gmail.com)\> wrote:
> 
> > Helloy everyone,
> > 
> > I have installed elasticsearch-1.0.1-1.noarch and  
> > logstash-1.3.3-flatjar.jar. I can't make logstash communicate to  
> > elasticsearch.
> > 
> > In elasticsearch.yml I have set just the cluster name (the rest is the  
> > default configuration). And I have this logstash.conf file (very simple):
> > 
> > input {  
> > file {  
> > type =\> "linux-syslog"  
> > path =\> ["/var/log/messages"]  
> > }  
> > }  
> > output {  
> > elasticsearch {  
> > embedded =\> false  
> > cluster =\> "my\_cluster"  
> > }  
> > }
> > 
> > Elasticsearch is running and for testing I execute:
> > 
> > java -jar /opt/logstash/logstash-1.3.3-flatjar.jar agent -f  
> > /opt/logstash/logstash.conf
> > 
> > But it doesn't work.
> > 
> > I can see in my\_cluster.log these errors:
> > 
> > [2014-02-27 17:34:34,863][WARN][discovery.zen.ping.multicast] [X-Man]  
> > failed to read requesting data from /192.168.13.17:54328  
> > java.io.IOException: No transport address mapped to [21345]  
> > at  
> > org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71)  
> > at  
> > org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267)  
> > at  
> > org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257)  
> > at  
> > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410)  
> > at java.lang.Thread.run(Thread.java:744)
> > 
> > And in the java execution screen:
> > 
> > log4j, [2014-02-27T17:35:01.851] WARN: org.elasticsearch.discovery:  
> > [Sabreclaw] waited for 30s and no initial state was set by the discovery
> > 
> > I assume they are not connecting each other (nodes with different names,  
> > failing request, no transport...).
> > 
> > Any idea about what is wrong with my elasticsearch + logstash  
> > configuration?
> > 
> > Thank you very much in advanced.  
> > Kind regards.
> > 
> > Héctor Moreno Blanco.
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/CADa-AwcCq2uJJCX7HDNyvF7Ms0AHzYGE8t6Ws-ZPpVzPdiryvA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADa-AwcCq2uJJCX7HDNyvF7Ms0AHzYGE8t6Ws-ZPpVzPdiryvA%40mail.gmail.com)  
> .
> 
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624ZVW2KvARodBtcLzWocYfB8dt6RGpi0\_j4XXetDVC6A1g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZVW2KvARodBtcLzWocYfB8dt6RGpi0_j4XXetDVC6A1g%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![Sean\_Gallagher](https://avatars.discourse-cdn.com/v4/letter/s/f1d935/32.png) [@Sean\_Gallagher](https://discuss.elastic.co/u/Sean_Gallagher)
#### Post date: [February 27, 2014, 9:34pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/5 "2014-02-27T21:34:13Z")

</div>

Logstash 1.4 is due for release soon, and will include support for  
Elasticsearch 1.0.x.

On Thursday, February 27, 2014 1:16:37 PM UTC-5, Sean Clemmer wrote:

> Logstash 1.3.3 is meant to work with Elasticsearch 0.90.9. See "VERSION  
> NOTE" in [Elasticsearch output plugin | Logstash Reference [8.11] | Elastic](http://logstash.net/docs/1.3.3/outputs/elasticsearch)
> 
> On Thu, Feb 27, 2014 at 8:47 AM, Héctor Moreno Blanco \<  
> [hector.mor...@gmail.com](mailto:hector.mor...@gmail.com) \<javascript:\>\> wrote:
> 
> > Helloy everyone,
> > 
> > I have installed elasticsearch-1.0.1-1.noarch and  
> > logstash-1.3.3-flatjar.jar. I can't make logstash communicate to  
> > elasticsearch.
> > 
> > In elasticsearch.yml I have set just the cluster name (the rest is the  
> > default configuration). And I have this logstash.conf file (very simple):
> > 
> > input {  
> > file {  
> > type =\> "linux-syslog"  
> > path =\> ["/var/log/messages"]  
> > }  
> > }  
> > output {  
> > elasticsearch {  
> > embedded =\> false  
> > cluster =\> "my\_cluster"  
> > }  
> > }
> > 
> > Elasticsearch is running and for testing I execute:
> > 
> > java -jar /opt/logstash/logstash-1.3.3-flatjar.jar agent -f  
> > /opt/logstash/logstash.conf
> > 
> > But it doesn't work.
> > 
> > I can see in my\_cluster.log these errors:
> > 
> > [2014-02-27 17:34:34,863][WARN][discovery.zen.ping.multicast] [X-Man]  
> > failed to read requesting data from /192.168.13.17:54328  
> > java.io.IOException: No transport address mapped to [21345]  
> > at  
> > org.elasticsearch.common.transport.TransportAddressSerializers.addressFromStream(TransportAddressSerializers.java:71)  
> > at  
> > org.elasticsearch.cluster.node.DiscoveryNode.readFrom(DiscoveryNode.java:267)  
> > at  
> > org.elasticsearch.cluster.node.DiscoveryNode.readNode(DiscoveryNode.java:257)  
> > at  
> > org.elasticsearch.discovery.zen.ping.multicast.MulticastZenPing$Receiver.run(MulticastZenPing.java:410)  
> > at java.lang.Thread.run(Thread.java:744)
> > 
> > And in the java execution screen:
> > 
> > log4j, [2014-02-27T17:35:01.851] WARN: org.elasticsearch.discovery:  
> > [Sabreclaw] waited for 30s and no initial state was set by the discovery
> > 
> > I assume they are not connecting each other (nodes with different names,  
> > failing request, no transport...).
> > 
> > Any idea about what is wrong with my elasticsearch + logstash  
> > configuration?
> > 
> > Thank you very much in advanced.  
> > Kind regards.
> > 
> > Héctor Moreno Blanco.
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fe368303-bea5-44d3-beed-c543b56be214%40googlegroups.com)  
> > .  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1a968e11-8493-4d8e-b16d-a1146fc474c5%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1a968e11-8493-4d8e-b16d-a1146fc474c5%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![Tony\_Su](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@Tony\_Su](https://discuss.elastic.co/u/Tony_Su)
#### Post date: [February 28, 2014, 3:17pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/6 "2014-02-28T15:17:27Z")

</div>

If it's not obvious, Mark's comment is exactly what you need to do,

Replace in the logstash output

elasticsearch

with

elasticsearch\_http

This and other things you may want to know if you're running the logstash tutorials are included in a wiki I posted  
[http://en.opensuse.org/User:Tsu2/elasticsearch\_1.0](http://en.opensuse.org/User:Tsu2/elasticsearch_1.0)

Tony

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2f6ffea0-8720-4f39-885c-49161f487902%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2f6ffea0-8720-4f39-885c-49161f487902%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

### Author: ![Hector\_Moreno\_Blanco](https://avatars.discourse-cdn.com/v4/letter/h/f08c70/32.png) [@Hector\_Moreno\_Blanco](https://discuss.elastic.co/u/Hector_Moreno_Blanco)
#### Post date: [February 28, 2014, 3:27pm UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/7 "2014-02-28T15:27:57Z")

</div>

Hello everybody,

Thank you for the help and advices.  
I think I'll try first the change of versions. When it works, I'll give  
elasticsearch\_http a try.

thank you very much.  
Kind regards.

Héctor Moreno  
El 28/02/2014 16:17, "Tony Su" [tonysu999@gmail.com](mailto:tonysu999@gmail.com) escribió:

> If it's not obvious, Mark's comment is exactly what you need to do,
> 
> Replace in the logstash output
> 
> elasticsearch
> 
> with
> 
> elasticsearch\_http
> 
> This and other things you may want to know if you're running the logstash  
> tutorials are included in a wiki I posted  
> [User:Tsu2/elasticsearch 1.0 - openSUSE Wiki](http://en.opensuse.org/User:Tsu2/elasticsearch_1.0)
> 
> Tony
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/UqwUXHZQ7Hk/unsubscribe](https://groups.google.com/d/topic/elasticsearch/UqwUXHZQ7Hk/unsubscribe).  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/2f6ffea0-8720-4f39-885c-49161f487902%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2f6ffea0-8720-4f39-885c-49161f487902%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAD4-sc\_e1fPdgnO7eGzX%3DCFfb%2BVYa%2BQcUKKUbFX74m6vEGcOcA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAD4-sc_e1fPdgnO7eGzX%3DCFfb%2BVYa%2BQcUKKUbFX74m6vEGcOcA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 1:46am UTC](https://discuss.elastic.co/t/logstash-and-elastisearch-doesnt-communicate/16055/8 "2017-07-06T01:46:35Z")

</div>


