my logstash conf file:
input {
beats {
port => 5044
}
}
output{
elasticsearch {
hosts => "localhost:9200"
index => "reshma"
user=> elastic
password=>elastic
}
stdout{codec => rubydebug}
}
Debug logs:
cfgfile/reload.go:77 BETA: Dynamic config reload is enabled.
2018-05-24T09:57:55.518+0530 INFO crawler/crawler.go:82 Loading and starting Prospectors completed. Enabled prospectors: 1
2018-05-24T09:57:55.518+0530 INFO cfgfile/reload.go:127 Config reloader started
2018-05-24T09:57:55.520+0530 INFO log/harvester.go:216 Harvester started for file: C:\Users\rmorampu\Documents\My Received Files\sample.log
2018-05-24T09:57:58.591+0530 ERROR pipeline/output.go:74 Failed to connect: dial tcp 127.0.0.1:5044: connectex: No connection could be made because the target machine actively refused it.
2018-05-24T09:58:02.622+0530 ERROR pipeline/output.go:74 Failed to connect: dial tcp 127.0.0.1:5044: connectex: No connection could be made because the target machine actively refused it.
2018-05-24T09:58:08.660+0530 ERROR pipeline/output.go:74 Failed to connect: dial tcp [::1]:5044: connectex: No connection could be made because the target machine actively refused it.
@remo You can verify the log shipment from Filebeat to Logstash without using Elasticsearch. Sometime if Elasticsearch is not working properly with Logstash then this kind of problem may arise.
You can verify it by following below steps:
Configure stdout in output section of logstash output { stdout{} }
Restart Logstash
Run Filebeat
[Note : If it is working fine then it is the problem regarding Elasticsearch and Logstash]
You can Follow the start sequence accordingly
Elasticsearch --> Logstash --> Filebeat
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.