# ES sniffing in logstash 2.1 vs 2.0

**URL:** <https://discuss.elastic.co/t/es-sniffing-in-logstash-2-1-vs-2-0/36886>\
**Category:** Logstash\
**Created:** [December 10, 2015, 2:38pm UTC](https://discuss.elastic.co/t/es-sniffing-in-logstash-2-1-vs-2-0/36886 "2015-12-10T14:38:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [December 10, 2015, 2:38pm UTC](https://discuss.elastic.co/t/es-sniffing-in-logstash-2-1-vs-2-0/36886/1 "2015-12-10T14:38:50Z")

</div>

Updated from logstash 2.0 to 2.1 on a CentOS 6.7 box and now when launching it I found below issue. Am using sniffing to a ES cluster. Any hints, TIA?

> {:timestamp=\>"2015-12-10T15:31:31.852000+0100", :message=\>"undefined method `close' for #<Manticore::Client:0x10046f05>", :class=>"NoMethodError", :backtrace=>["/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/t ransport/transport/http/manticore.rb:115:in `\_\_close\_connections'", "org/jruby/RubyArray.java:1613:in `each'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/http/manticore.rb:115:in `\_\_cl  
> ose\_connections'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/elasticsearch/transport/transport/base.rb:99:in `__rebuild_connections'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.15/lib/ela sticsearch/transport/transport/base.rb:77:in `reload\_connections!'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch/http\_client.rb:85:in `sniff!'", "/opt/logstash/vendor/bundle/jrub y/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:73:in `start\_sniffing!'", "org/jruby/ext/thread/Mutex.java:149:in `synchronize'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsea rch-2.2.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:73:in `start\_sniffing!'", "org/jruby/RubyKernel.java:1479:in `loop'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch /http_client.rb:72:in `start\_sniffing!'"], :level=\>:error}

---

<div class="post-metadata">

**Author:** ![saylott](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@saylott](https://discuss.elastic.co/u/saylott)\
**Post date:** [December 11, 2015, 5:17pm UTC](https://discuss.elastic.co/t/es-sniffing-in-logstash-2-1-vs-2-0/36886/2 "2015-12-11T17:17:29Z")

</div>

I'm seeing something similar. I was previously running topbeats (1.0.0) direct into elasticsearch (2.1.0). Just added logstash (2.1.1) in between and getting this error. This is a new build so can't comment on if something has broken or changed between versions.

Setup is pretty much as per the documentation, as I've only just started testing.

I'm on Oracle Linux 6.6

---

<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:18am UTC](https://discuss.elastic.co/t/es-sniffing-in-logstash-2-1-vs-2-0/36886/3 "2017-07-06T05:18:49Z")

</div>