Discuss the Elastic Stack

ERR SSL client failed to connect with: dial tcp xxx.xxx.xx.xxx:5044: getsockopt: connection refused

Elastic Stack Beats

jyothi_ca (Jyothi Ca) September 14, 2018, 2:27pm 1

Hi,

We noticed above error message and logs are not getting shifted due to above error message
we checked for connectivity issue , there is not issue of network connectivity

jsoriano (Jaime Soriano) September 19, 2018, 10:39am 2

Did this error happen connecting to logstash? Could you also check logstash logs to see if some error appears there?
Could you share more details about your deployment and configuration?

Topic		Replies	Views	Activity
125: SSL client failed to connect with: dial tcp 192.168.37.147:5044: getsockopt: connection refused Beats filebeat	9	3173	September 18, 2018
Error: getsockopt: connection refused Logstash	2	1209	August 12, 2022
ERR SSL client failed to connect with: Logstash	12	2591	July 6, 2017
Filebeat can't talk to logstash with connection refused error Beats filebeat	5	30988	July 26, 2016
Transport.go:125: ssl client failed to connect Beats	4	1850	March 5, 2018

© 2020. All Rights Reserved - Elasticsearch

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

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.