Logstash 5.6.0 not starting


(Kamal) #1

Hello,

I have 3 ES server running in cluster. I have x-pack install on all 3 ES, kibana and LS. They all are running ver 5.6.0

I am getting following error

[2017-09-20T17:45:14,760][FATAL][logstash.runner ] An unexpected error occurred! {:error=>#<Errno::EADDRNOTAVAIL: Cannot assign requested address - bind - Cannot assign requested address>, :backtrace=>["org/jruby/ext/socket/RubyTCPServer.java:118:in initialize'", "org/jruby/RubyIO.java:871:innew'", "/opt/elastic/logstash-5.6.0/vendor/bundle/jruby/1.9/gems/puma-2.16.0-java/lib/puma/binder.rb:234:in add_tcp_listener'", "(eval):2:inadd_tcp_listener'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/webserver.rb:88:in start_webserver'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/webserver.rb:44:inrun'", "org/jruby/RubyRange.java:476:in each'", "org/jruby/RubyEnumerable.java:971:ineach_with_index'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/webserver.rb:39:in run'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/agent.rb:222:instart_webserver'"]}

in my logstash.yml file, I have the following

http.host: "10.24.240.253"
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.url: "http://10.24.240.253:9200"
xpack.monitoring.elasticsearch.username: "logstash_internal"
xpack.monitoring.elasticsearch.password: "k3yb4nkelk"

I am running LS on the on one of the 3 ES node.

my conf file is very simple

input {

stdin {}
}

output {

stdout{}
}

Any help will be appricaiated


(Mark Walkom) #2

What happens if you uncomment that?


(Kamal) #3

It works in a sense that I do not get the FATAL error and I am getting the data in splunk but I see the following error now

[2017-09-20T19:44:49,742][ERROR][logstash.outputs.elasticsearch] Encountered an unexpected error submitting a bulk request! Will retry. {:error_message=>"undefined method sanitized' for #<String:0x74f34347>", :class=>"NoMethodError", :backtrace=>["/opt/elastic/logstash-5.6.0/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:249:insafe_bulk'", "/opt/elastic/logstash-5.6.0/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:119:in submit'", "/opt/elastic/logstash-5.6.0/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:87:inretrying_submit'", "/opt/elastic/logstash-5.6.0/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-7.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:38:in multi_receive'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/output_delegator_strategies/shared.rb:13:inmulti_receive'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/output_delegator.rb:49:in multi_receive'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/pipeline.rb:436:inoutput_batch'", "org/jruby/RubyHash.java:1342:in each'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/pipeline.rb:435:inoutput_batch'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/pipeline.rb:381:in worker_loop'", "/opt/elastic/logstash-5.6.0/logstash-core/lib/logstash/pipeline.rb:342:instart_workers'"]}


(Kamal) #4

sorry I mean data in Elastic.


(Mark Walkom) #5

Check your Elasticsearch logs, it should tell you something more.


(system) #6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.