Transport.go:125: ssl client failed to connect


(Pierre “What's Up” Scadra) #1

I am trying to connect filebeat to logstash but I have this error :
● filebeat.service - filebeat
Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2018-02-12 14:04:27 CET; 9min ago
Docs: https://www.elastic.co/guide/en/beats/filebeat/current/index.html
Main PID: 56013 (filebeat)
CGroup: /system.slice/filebeat.service
└─56013 /usr/bin/filebeat -c /etc/filebeat/filebeat.yml

Feb 12 14:04:58 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:05:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:06:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:07:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:08:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:09:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:10:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:11:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:12:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused
Feb 12 14:13:30 localhost.localdomain /usr/bin/filebeat[56013]: transport.go:125: SSL client failed to connect with: dial tcp 192.168.1.117:5044: getsockopt: connection refused

I have configured my filebeat like this :
tls:

  certificate_authorities: ["/etc/ssl/logstash_frwrd.crt"]

  # Certificate for TLS client authentication
  #certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #certificate_key: "/etc/pki/client/cert.key"

and my logstash :
#input section
input{
beats{
port=>5044
ssl=>true
ssl_certificate=>"/etc/ssl/logstash_frwrd.crt"
ssl_key=>"/etc/ssl/logstash-forwarder.key"
}
}


(Tudor Golubenco) #2

Can you run the following:

filebeat test output

From the error, it seems that you get a connection refused error, so perhaps Logstash is not actually running or running on a different IP?


(Pierre “What's Up” Scadra) #3

I have this error :
diap up... ERROR dial tcp 192.168.1.117:5044: getsockopt : connection refused

And the status of logstash is running ...


(Tudor Golubenco) #4

I assume also telnet 192.168.1.117 5044 gives a connection refused, right? It looks like a connectivity issue. I'd recommend first trying telnet localhost 5044 on the LS machine to make sure the port is locally reachable. Then run netstat -nlp | grep 5044 on the LS machine to check that LS is listening on the right IP address.


(system) #5

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