I am unable to access Logstash(windows service) through http://localhost:5044 (within the logstash server) and also unable to access http://192.168.27.189:5044 (outside of the logstash server)


(Dinesh Krishnaswamy) #1

I am unable to access Logstash(windows service) through http://localhost:5044 (within the logstash server) and also unable to access http://192.168.27.189:5044 (outside of the logstash server)

  1. I can see Logstash windows service is up and running
  2. 'Telnet localhost 5044' is connection failed(within the logstash server)
  3. 'Telnet 192.168.27.189 5044' is connection failed(outside of the logstash server)
  4. I dont see any error logged in the log file
  5. Here is the logstash.conf

input {
beats {
port => "5044"
type => "log"
}
}
output {
elasticsearch {
hosts => "192.168.27.189:9200"
manage_template => false
index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
document_type => "%{[@metadata][type]}"
}
}

  1. Logstash.yml - all are commented out
  2. pipeline.yml - every thing commented out.
  3. I did create new inbound fire wall rule to allow the connection for all the local ports.

(Magnus B├Ąck) #2

I am unable to access Logstash(windows service) through http://localhost:5044 (within the logstash server) and also unable to access http://192.168.27.189:5044 (outside of the logstash server)

The beats input doesn't provide HTTP service so http://localhost:5044 will never do anything useful.

Have you checked your Logstash log for clues? Maybe it's not start up properly.


(Dinesh Krishnaswamy) #3

I figured out the problem when I was installing logstash-input-beats it didnt install properly. When I installed, it worked. Sorry for this is unnecessary request.


(system) #4

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