Logstash 5 Alpha4 to elasticsearch5 Alpha4 communication error

Question

Elasticsearch 5 is protected by xpack and is connected to ldap, which works fine. Even the user has administrator rights in role_mapping .

Logstash 5 configuration is below

 output { elasticsearch { hosts => ['localhost:9200'] user => ' [e-mail] ' password => 'pwd' } } 

The following is an error and due to which logstash cannot transmit data to elasticsearch.

 {:timestamp=>"2016-07-14T16:32:29.592000+0530", :message=>"Encountered an unexpected error submitting a bulk request! Will retry.", :error_message=>"undefined method code' for #", :class=>"NoMethodError", :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-4.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:217:insafe_bulk'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-4.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:105:in submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-4.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:72:inretrying_submit'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-4.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:23:in multi_receive'", "org/jruby/RubyArray.java:1653:ineach_slice'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-4.1.1-java/lib/logstash/outputs/elasticsearch/common.rb:22:in multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb:136:inthreadsafe_multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_ 

Answer 1

I think I may have figured this out. I am using the Logstash 5.1.1-alpine docker image. As far as I can tell, it comes with an elasticsearch-output v4.5.0 plugin that seems to have this error. Forcibly updating this plugin to the latest version (6.2) fixed this problem.

My dockerfile now

 FROM logstash:5.1.1-alpine RUN $LOGSTASH_PATH/logstash-plugin install --version 6.2.0 logstash-output-elasticsearch 

With the updated plugin, I no longer see this error.