# ES and logstash are nit working well with each other

**URL:** <https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795>\
**Category:** Elasticsearch\
**Created:** [May 29, 2014, 4:43am UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795 "2014-05-29T04:43:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [May 29, 2014, 4:43am UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/1 "2014-05-29T04:43:34Z")

</div>

Hi,

I am, rather concerned that ES is not working with logstash index server.

I start logstash index server like this:

/usr/local/share/logstash-1.4.1/bin/logstash -f  
/usr/local/share/logstash.indexer.config

Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
if you see strange behavior, please let us know! For more information on  
plugin milestones, see  
[http://logstash.net/docs/1.4.1/plugin-milestones{:level=\>:warn}](http://logstash.net/docs/1.4.1/plugin-milestones%7B:level=%3E:warn%7D)  
log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery:  
[logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for  
30s and no initial state was set by the discovery  
Exception in thread "\>output"  
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
at  
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
at  
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(java/lang/Thread.java:744)

Here is my config:

input {  
redis {  
host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
data\_type =\> "list"  
key =\> "logstash"  
codec =\> json  
}  
}

output {  
stdout { }  
elasticsearch {  
host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
}  
}

Yes..ES us running and Yes ports are open for logstash

So..whats the deal?

Thanks

--  
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/CACF%2B8rpLhKKFPv%2BZ\_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpLhKKFPv%2BZ_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [May 29, 2014, 4:45am UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/2 "2014-05-29T04:45:40Z")

</div>

You should take this to the LS group for the best response 🙂

But, is ES running?

Regards,  
Mark Walkom

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

On 29 May 2014 14:43, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) wrote:

> Hi,
> 
> I am, rather concerned that ES is not working with logstash index server.
> 
> I start logstash index server like this:
> 
> /usr/local/share/logstash-1.4.1/bin/logstash -f  
> /usr/local/share/logstash.indexer.config
> 
> Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
> if you see strange behavior, please let us know! For more information on  
> plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones%7B:level=%3E:warn%7D)  
> log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery:  
> [logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for  
> 30s and no initial state was set by the discovery  
> Exception in thread "\>output"  
> org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> at  
> org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> at  
> org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(java/lang/Thread.java:744)
> 
> Here is my config:
> 
> input {  
> redis {  
> host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> data\_type =\> "list"  
> key =\> "logstash"  
> codec =\> json  
> }  
> }
> 
> output {  
> stdout { }  
> elasticsearch {  
> host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
> }  
> }
> 
> Yes..ES us running and Yes ports are open for logstash
> 
> So..whats the deal?
> 
> Thanks
> 
> --  
> 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/CACF%2B8rpLhKKFPv%2BZ\_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpLhKKFPv%2BZ_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com)[https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpLhKKFPv%2BZ\_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpLhKKFPv%2BZ_JpwiR%3DuNUJLrjm7PGQ0z6dR%2BF04dBytyQ%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEM624ZwKqR32YuDFhkXmHFKqGciXkZ4WQ437Sn78Mwyd6Yhxg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624ZwKqR32YuDFhkXmHFKqGciXkZ4WQ437Sn78Mwyd6Yhxg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [May 29, 2014, 5:15am UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/3 "2014-05-29T05:15:42Z")

</div>

PS...and how is this possible????? I feel so bad I bought the kindle  
logstash book:(

I changed to host rather than bind host. I mean..wow..I have ports open.  
See? ufw satus ===\> 9200:9400/tcp ALLOW  
my.logstash.ipaddress

I have ES running  
service elasticsearch status

- elasticsearch is running

/usr/local/share/logstash-1.4.1/bin/logstash -f  
/usr/local/share/logstash.indexer.configUsing milestone 2 input plugin  
'redis'. This plugin should be stable, but if you see strange behavior,  
please let us know! For more information on plugin milestones, see  
[Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
Exception in thread "\>output"  
org.elasticsearch.transport.BindTransportException: Failed to bind to  
[9300-9400]  
at  
org.elasticsearch.transport.netty.NettyTransport.doStart(org/elasticsearch/transport/netty/NettyTransport.java:380)  
at  
org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
at  
org.elasticsearch.transport.TransportService.doStart(org/elasticsearch/transport/TransportService.java:92)  
at  
org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
at  
org.elasticsearch.node.internal.InternalNode.start(org/elasticsearch/node/internal/InternalNode.java:229)  
at  
org.elasticsearch.node.NodeBuilder.node(org/elasticsearch/node/NodeBuilder.java:166)  
at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)  
at  
RUBY.build\_client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:198)  
at  
RUBY.client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:15)  
at  
RUBY.initialize(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:157)  
at  
RUBY.register(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch.rb:250)  
at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)  
at  
RUBY.outputworker(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:220)  
at  
RUBY.start\_outputs(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:152)  
at java.lang.Thread.run(java/lang/Thread.java:744)

On Thu, May 29, 2014 at 12:43 PM, David Montgomery \<  
[davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:

> Hi,
> 
> I am, rather concerned that ES is not working with logstash index server.
> 
> I start logstash index server like this:
> 
> /usr/local/share/logstash-1.4.1/bin/logstash -f  
> /usr/local/share/logstash.indexer.config
> 
> Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
> if you see strange behavior, please let us know! For more information on  
> plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones%7B:level=%3E:warn%7D)  
> log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery:  
> [logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for  
> 30s and no initial state was set by the discovery  
> Exception in thread "\>output"  
> org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> at  
> org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> at  
> org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(java/lang/Thread.java:744)
> 
> Here is my config:
> 
> input {  
> redis {  
> host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> data\_type =\> "list"  
> key =\> "logstash"  
> codec =\> json  
> }  
> }
> 
> output {  
> stdout { }  
> elasticsearch {  
> host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
> }  
> }
> 
> Yes..ES us running and Yes ports are open for logstash
> 
> So..whats the deal?
> 
> Thanks

--  
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/CACF%2B8rpwG%3D3n3PPpsqBhsDFTm9t9tbMTkhwNSAx%2BuForbGHgrg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwG%3D3n3PPpsqBhsDFTm9t9tbMTkhwNSAx%2BuForbGHgrg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![David\_Montgomery](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@David\_Montgomery](https://discuss.elastic.co/u/David_Montgomery)\
**Post date:** [May 29, 2014, 3:21pm UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/4 "2014-05-29T15:21:36Z")

</div>

Before I give up on logstash..I now placed Elasticsearch on the same  
server using the below.

input {  
redis {  
host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
data\_type =\> "list"  
key =\> "logstash"  
codec =\> json  
}  
}

output {  
stdout { }  
elasticsearch {  
bind\_host =\> "127.0.0.1"  
}  
}

I get this erorr I am using 1.4.1for logstash and  
0.90.9 for es.

'/usr/local/share/logstash-1.4.1/bin/logstash -f  
/usr/local/share/logstash.indexer.config  
Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
if you see strange behavior, please let us know! For more information on  
plugin milestones, see

> **[Logstash: Collect, Parse, Transform Logs | Elastic](https://www.elastic.co/logstash)**
>
> Logstash (part of the Elastic Stack) integrates data from any source, in any format with this flexible, open source collection, parsing, and enrichment pipeline. Download for free.

log4j, [2014-05-29T11:18:31.923] WARN: org.elasticsearch.discovery:  
[logstash-do-logstash-sf-development-20140527082230-16645-2010] waited for  
30s and no initial state was set by the discovery  
Exception in thread "\>output"  
org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
at  
org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
at  
org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
at  
java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(java/lang/Thread.java:744)

On Thu, May 29, 2014 at 1:15 PM, David Montgomery \<[davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)

> wrote:

> PS...and how is this possible????? I feel so bad I bought the kindle  
> logstash book:(
> 
> I changed to host rather than bind host. I mean..wow..I have ports open.  
> See? ufw satus ===\> 9200:9400/tcp ALLOW  
> my.logstash.ipaddress
> 
> I have ES running  
> service elasticsearch status
> 
> - elasticsearch is running
> 
> /usr/local/share/logstash-1.4.1/bin/logstash -f  
> /usr/local/share/logstash.indexer.configUsing milestone 2 input plugin  
> 'redis'. This plugin should be stable, but if you see strange behavior,  
> please let us know! For more information on plugin milestones, see  
> [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
> Exception in thread "\>output"  
> org.elasticsearch.transport.BindTransportException: Failed to bind to  
> [9300-9400]  
> at  
> org.elasticsearch.transport.netty.NettyTransport.doStart(org/elasticsearch/transport/netty/NettyTransport.java:380)  
> at  
> org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> at  
> org.elasticsearch.transport.TransportService.doStart(org/elasticsearch/transport/TransportService.java:92)  
> at  
> org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> at  
> org.elasticsearch.node.internal.InternalNode.start(org/elasticsearch/node/internal/InternalNode.java:229)  
> at  
> org.elasticsearch.node.NodeBuilder.node(org/elasticsearch/node/NodeBuilder.java:166)  
> at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)  
> at  
> RUBY.build\_client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:198)  
> at  
> RUBY.client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:15)  
> at  
> RUBY.initialize(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:157)  
> at  
> RUBY.register(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch.rb:250)  
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)  
> at  
> RUBY.outputworker(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:220)  
> at  
> RUBY.start\_outputs(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:152)  
> at java.lang.Thread.run(java/lang/Thread.java:744)
> 
> On Thu, May 29, 2014 at 12:43 PM, David Montgomery \<  
> [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> 
> > Hi,
> > 
> > I am, rather concerned that ES is not working with logstash index server.
> > 
> > I start logstash index server like this:
> > 
> > /usr/local/share/logstash-1.4.1/bin/logstash -f  
> > /usr/local/share/logstash.indexer.config
> > 
> > Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
> > if you see strange behavior, please let us know! For more information on  
> > plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones%7B:level=%3E:warn%7D)  
> > log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery:  
> > [logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for  
> > 30s and no initial state was set by the discovery  
> > Exception in thread "\>output"  
> > org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> > at  
> > org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> > at  
> > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> > at  
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(java/lang/Thread.java:744)
> > 
> > Here is my config:
> > 
> > input {  
> > redis {  
> > host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> > data\_type =\> "list"  
> > key =\> "logstash"  
> > codec =\> json  
> > }  
> > }
> > 
> > output {  
> > stdout { }  
> > elasticsearch {  
> > host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
> > }  
> > }
> > 
> > Yes..ES us running and Yes ports are open for logstash
> > 
> > So..whats the deal?
> > 
> > Thanks

--  
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/CACF%2B8rpwPQuRkxD12GNp5eS\_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwPQuRkxD12GNp5eS_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 29, 2014, 3:38pm UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/5 "2014-05-29T15:38:39Z")

</div>

Elasticsearch output is using es 1.x IIRC. You can not mix versions.  
You need to upgrade es or downgrade logstash or use elasticsearch HTTP output.

My 2 cents

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 29 mai 2014 à 17:21, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a écrit :

Before I give up on logstash..I now placed Elasticsearch on the same server using the below.

input {  
redis {  
host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
data\_type =\> "list"  
key =\> "logstash"  
codec =\> json  
}  
}

output {  
stdout { }  
elasticsearch {  
bind\_host =\> "127.0.0.1"  
}  
}

I get this erorr I am using 1.4.1for logstash and  
0.90.9 for es.

'/usr/local/share/logstash-1.4.1/bin/logstash -f /usr/local/share/logstash.indexer.config  
Using milestone 2 input plugin 'redis'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
log4j, [2014-05-29T11:18:31.923] WARN: org.elasticsearch.discovery: [logstash-do-logstash-sf-development-20140527082230-16645-2010] waited for 30s and no initial state was set by the discovery  
Exception in thread "\>output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
at org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(java/lang/Thread.java:744)

> On Thu, May 29, 2014 at 1:15 PM, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) wrote:  
> PS...and how is this possible????? I feel so bad I bought the kindle logstash book:(
> 
> I changed to host rather than bind host. I mean..wow..I have ports open. See? ufw satus ===\> 9200:9400/tcp ALLOW my.logstash.ipaddress
> 
> I have ES running  
> service elasticsearch status
> 
> - elasticsearch is running
> 
> /usr/local/share/logstash-1.4.1/bin/logstash -f /usr/local/share/logstash.indexer.configUsing milestone 2 input plugin 'redis'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
> Exception in thread "\>output" org.elasticsearch.transport.BindTransportException: Failed to bind to [9300-9400]  
> at org.elasticsearch.transport.netty.NettyTransport.doStart(org/elasticsearch/transport/netty/NettyTransport.java:380)  
> at org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> at org.elasticsearch.transport.TransportService.doStart(org/elasticsearch/transport/TransportService.java:92)  
> at org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> at org.elasticsearch.node.internal.InternalNode.start(org/elasticsearch/node/internal/InternalNode.java:229)  
> at org.elasticsearch.node.NodeBuilder.node(org/elasticsearch/node/NodeBuilder.java:166)  
> at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)  
> at RUBY.build\_client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:198)  
> at RUBY.client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:15)  
> at RUBY.initialize(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:157)  
> at RUBY.register(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch.rb:250)  
> at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)  
> at RUBY.outputworker(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:220)  
> at RUBY.start\_outputs(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:152)  
> at java.lang.Thread.run(java/lang/Thread.java:744)
> 
> > On Thu, May 29, 2014 at 12:43 PM, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) wrote:  
> > Hi,
> > 
> > I am, rather concerned that ES is not working with logstash index server.
> > 
> > I start logstash index server like this:
> > 
> > /usr/local/share/logstash-1.4.1/bin/logstash -f /usr/local/share/logstash.indexer.config
> > 
> > Using milestone 2 input plugin 'redis'. This plugin should be stable, but if you see strange behavior, please let us know! For more information on plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
> > log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery: [logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for 30s and no initial state was set by the discovery  
> > Exception in thread "\>output" org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> > at org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> > at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> > at java.lang.Thread.run(java/lang/Thread.java:744)
> > 
> > Here is my config:
> > 
> > input {  
> > redis {  
> > host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> > data\_type =\> "list"  
> > key =\> "logstash"  
> > codec =\> json  
> > }  
> > }
> > 
> > output {  
> > stdout { }  
> > elasticsearch {  
> > host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
> > }  
> > }
> > 
> > Yes..ES us running and Yes ports are open for logstash
> > 
> > So..whats the deal?
> > 
> > Thanks

--  
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/CACF%2B8rpwPQuRkxD12GNp5eS\_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwPQuRkxD12GNp5eS_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [May 29, 2014, 10:20pm UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/6 "2014-05-29T22:20:10Z")

</div>

Use the HTTP output and save yourself some trouble.

Also, upgrade ES 🙂

Regards,  
Mark Walkom

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

On 30 May 2014 01:38, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> Elasticsearch output is using es 1.x IIRC. You can not mix versions.  
> You need to upgrade es or downgrade logstash or use elasticsearch HTTP  
> output.
> 
> My 2 cents
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 29 mai 2014 à 17:21, David Montgomery [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com) a  
> écrit :
> 
> Before I give up on logstash..I now placed Elasticsearch on the same  
> server using the below.
> 
> input {  
> redis {  
> host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> data\_type =\> "list"  
> key =\> "logstash"  
> codec =\> json  
> }  
> }
> 
> output {  
> stdout { }  
> elasticsearch {  
> bind\_host =\> "127.0.0.1"  
> }  
> }
> 
> I get this erorr I am using 1.4.1for logstash and  
> 0.90.9 for es.
> 
> '/usr/local/share/logstash-1.4.1/bin/logstash -f  
> /usr/local/share/logstash.indexer.config  
> Using milestone 2 input plugin 'redis'. This plugin should be stable, but  
> if you see strange behavior, please let us know! For more information on  
> plugin milestones, see [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones)  
> {:level=\>:warn}  
> log4j, [2014-05-29T11:18:31.923] WARN: org.elasticsearch.discovery:  
> [logstash-do-logstash-sf-development-20140527082230-16645-2010] waited for  
> 30s and no initial state was set by the discovery  
> Exception in thread "\>output"  
> org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> at  
> org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> at  
> org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> at  
> java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> at  
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(java/lang/Thread.java:744)
> 
> On Thu, May 29, 2014 at 1:15 PM, David Montgomery \<  
> [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> 
> > PS...and how is this possible????? I feel so bad I bought the kindle  
> > logstash book:(
> > 
> > I changed to host rather than bind host. I mean..wow..I have ports  
> > open. See? ufw satus ===\> 9200:9400/tcp ALLOW  
> > my.logstash.ipaddress
> > 
> > I have ES running  
> > service elasticsearch status
> > 
> > - elasticsearch is running
> > 
> > /usr/local/share/logstash-1.4.1/bin/logstash -f  
> > /usr/local/share/logstash.indexer.configUsing milestone 2 input plugin  
> > 'redis'. This plugin should be stable, but if you see strange behavior,  
> > please let us know! For more information on plugin milestones, see  
> > [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
> > Exception in thread "\>output"  
> > org.elasticsearch.transport.BindTransportException: Failed to bind to  
> > [9300-9400]  
> > at  
> > org.elasticsearch.transport.netty.NettyTransport.doStart(org/elasticsearch/transport/netty/NettyTransport.java:380)  
> > at  
> > org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> > at  
> > org.elasticsearch.transport.TransportService.doStart(org/elasticsearch/transport/TransportService.java:92)  
> > at  
> > org.elasticsearch.common.component.AbstractLifecycleComponent.start(org/elasticsearch/common/component/AbstractLifecycleComponent.java:85)  
> > at  
> > org.elasticsearch.node.internal.InternalNode.start(org/elasticsearch/node/internal/InternalNode.java:229)  
> > at  
> > org.elasticsearch.node.NodeBuilder.node(org/elasticsearch/node/NodeBuilder.java:166)  
> > at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:606)  
> > at  
> > RUBY.build\_client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:198)  
> > at  
> > RUBY.client(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:15)  
> > at  
> > RUBY.initialize(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch/protocol.rb:157)  
> > at  
> > RUBY.register(/usr/local/share/logstash-1.4.1/lib/logstash/outputs/elasticsearch.rb:250)  
> > at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1613)  
> > at  
> > RUBY.outputworker(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:220)  
> > at  
> > RUBY.start\_outputs(/usr/local/share/logstash-1.4.1/lib/logstash/pipeline.rb:152)  
> > at java.lang.Thread.run(java/lang/Thread.java:744)
> > 
> > On Thu, May 29, 2014 at 12:43 PM, David Montgomery \<  
> > [davidmontgomery@gmail.com](mailto:davidmontgomery@gmail.com)\> wrote:
> > 
> > > Hi,
> > > 
> > > I am, rather concerned that ES is not working with logstash index server.
> > > 
> > > I start logstash index server like this:
> > > 
> > > /usr/local/share/logstash-1.4.1/bin/logstash -f  
> > > /usr/local/share/logstash.indexer.config
> > > 
> > > Using milestone 2 input plugin 'redis'. This plugin should be stable,  
> > > but if you see strange behavior, please let us know! For more information  
> > > on plugin milestones, see  
> > > [Logstash: Collect, Parse, Transform Logs | Elastic](http://logstash.net/docs/1.4.1/plugin-milestones) {:level=\>:warn}  
> > > log4j, [2014-05-29T00:33:12.473] WARN: org.elasticsearch.discovery:  
> > > [logstash-do-logstash-sf-development-20140527082230-2162-2010] waited for  
> > > 30s and no initial state was set by the discovery  
> > > Exception in thread "\>output"  
> > > org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s]  
> > > at  
> > > org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$3.onTimeout(org/elasticsearch/action/support/master/TransportMasterNodeOperationAction.java:180)  
> > > at  
> > > org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(org/elasticsearch/cluster/service/InternalClusterService.java:492)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(java/util/concurrent/ThreadPoolExecutor.java:1145)  
> > > at  
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(java/util/concurrent/ThreadPoolExecutor.java:615)  
> > > at java.lang.Thread.run(java/lang/Thread.java:744)
> > > 
> > > Here is my config:
> > > 
> > > input {  
> > > redis {  
> > > host =\> "[redis.queue.do.development.sf.test.com](http://redis.queue.do.development.sf.test.com)"  
> > > data\_type =\> "list"  
> > > key =\> "logstash"  
> > > codec =\> json  
> > > }  
> > > }
> > > 
> > > output {  
> > > stdout { }  
> > > elasticsearch {  
> > > host =\> "[eslogs.do.development.sf.test.com](http://eslogs.do.development.sf.test.com)"  
> > > }  
> > > }
> > > 
> > > Yes..ES us running and Yes ports are open for logstash
> > > 
> > > So..whats the deal?
> > > 
> > > Thanks
> 
> --  
> 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/CACF%2B8rpwPQuRkxD12GNp5eS\_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwPQuRkxD12GNp5eS_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwPQuRkxD12GNp5eS\_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CACF%2B8rpwPQuRkxD12GNp5eS_u5%3D%2Bdz-6f5Go1-pQtjnWa76iMg%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> 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/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr)  
> [https://groups.google.com/d/msgid/elasticsearch/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/7A285E35-E405-456B-B739-C47115D37312%40pilato.fr?utm_medium=email&utm_source=footer)  
> .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEM624aEk8nEWphE6yEZQ9LtGGNBfq%3DB1Dm5ZSmjME-HmPRouQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624aEk8nEWphE6yEZQ9LtGGNBfq%3DB1Dm5ZSmjME-HmPRouQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:26am UTC](https://discuss.elastic.co/t/es-and-logstash-are-nit-working-well-with-each-other/17795/7 "2017-07-06T01:26:00Z")

</div>