Can not make TLS/SSL connection to kafka v0,9 using filebeat v5


(Cheng Tao Chen) #1

Hi:

I am trying to figure out how to make TLS/SSL connection from filebeat v5. I have enabled TLS and client authentication on a Kafka v0.9 server, and configure filebeat with TLS enabled, but I am getting tons of TLS error:

2016/06/18 19:27:10.445168 publish.go:92: INFO Start sending events to output
2016/06/18 19:27:15.446180 log.go:16: WARN kafka message: Initializing new client
2016/06/18 19:27:15.446275 log.go:12: WARN client/metadata fetching metadata for all topics from broker 10.241.227.122:9092
2016/06/18 19:27:15.454176 log.go:12: WARN Failed to connect to broker 10.241.227.122:9092: tls: first record does not look like a TLS handshake
2016/06/18 19:27:15.454357 log.go:16: WARN kafka message: client/metadata got error from broker while fetching metadata:%!(EXTRA tls.RecordHeaderError=tls: first record does not look like a TLS handshake)
2016/06/18 19:27:15.454505 log.go:16: WARN kafka message: client/metadata no available broker to send metadata request to
2016/06/18 19:27:15.454582 log.go:12: WARN client/brokers resurrecting 1 dead seed brokers
2016/06/18 19:27:15.454689 log.go:12: WARN client/metadata retrying after 250ms... (3 attempts remaining)

Just wondering have anybody successfully configure filebeat v 5 to connect to kafka v 0.9 through TLS/SSL?


Error Return code 21: SSL encryption between filebeat 5.2 and kafka 1.0 (self signed)
(Steffen Siering) #2

Looks like kafka is not configured properly. The TLS connection setup fails, due to kafka endpoint not using TLS. Have you enabled SSL support in kafka? You pointing beats to correct ports?

Seems like bootstrap brokers can not be accessed already. Once this is possible, make sure all kafka brokers to advertise the correct host and port.


(system) #3

This topic was automatically closed after 21 days. New replies are no longer allowed.