Hello @all ,
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:
https://discuss.elastic.co/t/filebeat-on-windows-ssl-certificates/125333/2
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.
jsoriano
(Jaime Soriano)
June 5, 2018, 8:56am
2
Hi @SimonSays4223 ,
Welcome to the discuss forum
The configuration looks good . Could you check the filebeat logs to see if it is reporting any error there?
jsoriano
(Jaime Soriano)
June 5, 2018, 9:03am
3
Could you try to scape the path separators? Like this:
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"
You can also use single quoutes instead:
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'
2 Likes
Nice. that worked... now filebeat is starting.
Thanks a lot!
1 Like
system
(system)
Closed
July 3, 2018, 9:24am
5
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.