Error while starting Logstash

Elastic Stack Logstash
1

Hello,
I'm having ELK 5.6.2.My environment like below,

FileBeat(Machine A) => Logstash (Machine B) => Elasticsearch (Machine B) => Kibana (Machine B)

I have configured Logstash as output.

#----------------------------- Logstash output ---------------------------------
output.logstash:
enabled: true
hosts: ["IP of Machine B:5044"]
ssl.enabled: false

My Logstash pipeline like,

input {
beats {
port => 5044
ssl => false
}
}

output {
elasticsearch {
hosts => ["IP of Machine B:9200"]
sniffing => true
manage_template => false
index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
document_type => "%{[@metadata][type]}"
}
}

My Logstash.yml like,

------------ Node identity ------------

node.name: QALogParser

------------ Metrics Settings --------------

http.host: "IP of Machine B"

While I start logstash I got below error,

][INFO ][logstash.inputs.beats ] Beats inputs: Starting input listener {:address=>"0.0.0.0:5044"}
[2017-10-25T19:45:33,594][INFO ][logstash.pipeline ] Pipeline main started
[2017-10-25T19:45:33,715][INFO ][org.logstash.beats.Server] Starting server on port: 5044
[2017-10-25T19:45:33,862][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:in new'", "/opt/Logger/Logstash/vendor/bundle/jruby/1.9/gems/puma-2.16.0-java/lib/puma/binder.rb:234:in add_tcp_listener'", "(eval):2:in add_tcp_listener'", "/opt/Logger/Logstash/logstash-core/lib/logstash/webserver.rb:88:in start_webserver'", "/opt/Logger/Logstash/logstash-core/lib/logstash/webserver.rb:44:in run'", "org/jruby/RubyRange.java:476:in each'", "org/jruby/RubyEnumerable.java:971:in each_with_index'", "/opt/Logger/Logstash/logstash-core/lib/logstash/webserver.rb:39:in run'", "/opt/Logger/Logstash/logstash-core/lib/logstash/agent.rb:222:in start_webserver'"]}

Any suggestions?Thanks in advance.

2

Obvious question, is there anything else listening on that port number ?

netstat -anlp | grep 5044

3

Hi Jack,
5044 port not listening.

4

Issue solved :slight_smile: while I configure my pipeline like below,

input {
beats {
host => "Private IP of Machine B"
port => 5044
ssl => false
}
}

IP made an issue .

5

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