I'm trying to configure filebeat on a Win7 and Win10 machine with SSL-Certificates. After configuring it as described:
output.logstash hosts: ["mylogstaship:myport"] ssl.certificate_authorities: ["C:\filebeat-6.2.4-windows-x86_64\myrootca.crt"] ssl.certificate: "C:\filebeat-6.2.4-windows-x86_64\myclientcert.crt" ssl.key: "C:\filebeat-6.2.4-windows-x86_64\myclientkey.key"
I'm getting the following error:
The service filebeat cannot be startetd. Error 1053 ...
It always appears if I have a config mistake. When commenting the ssl-lines out, it works.
Seems to be the same issue as:
Since it has not been solved yet, I think the bug still exists. Unfortunately there is no logentry in the filebeat logging mechanism (event on debug) that could indicate why the config cannot be parsed.
PS: The same config on a CentOS6 and CentOS7 host just works fine.