Hi all,
I'm using the latest ELK-Stack (5.3.0) and installed ES, Kibana, and Logstash on the same machine (Win 2016 Server). In addition to that, I installed Filebeat on another machine (my notebook [Win 8.2]) that is reading a local log file and sending messages to logstash. On the one hand, ES and Kibana are working well. E.g. I'm able to use ES through the REST API to see all the indices and also, I'm able to see data from ES in Kibana. And Kibana is also monitoring my Logstash.
On the other hand, Logstash and Filebeat are also working well. When I update my logfile, I can see the new entry in the console of Logstash (stdout) as well as in the file (file output) on the server.
BUT using Elasticsearch as an (third) output for Logstash do not work at all. Although, I can see the new log entries in the stdout and the file output, Logstash do not write data to ES. In my Filebeat log, there is the following error occuring:
"ERR Failed to publish events caused by: write tcp xxx.xxx.xxx.47:64160->xxxxxx.xxx.168:5044: wsasend: An existing connection was forcibly closed by the remote host."
This is my Logstash conf:
input {
beats {
host => "xxx.xxx.xxx.168"
port => 5044
}
}
output {
elasticsearch {
hosts => "xxx.xxx.xxx.168:9200"
user => "elastic"
password => "<<very secure password>>"
}
stdout { codec => rubydebug }
file {
path => "\testLog.log"
create_if_deleted => true
}
}
The same problem also comes up, when I'm using Elastic search as the only output of Logstash.
I turned off all firewalls but this doesn't help. Neither the log file of Logstash, nor the logfile of Elastic search provide any further information about what is going wrong. All IP adresses and ports, as well as credentials provided in the config/yml-files were multiple checked.
I'm now struggling with that problem since days and I hope, that someone can provide me a helping hand.
Thank you very much!
Marcus