Filebeat is not able to connect to logstash

[NetRajan (Rajan Bhatt)]

I am using filebeat version 7.6.2
Trying to connect to logstash and getting following error.

Failed to connect to backoff(async(tcp://dnslogstash.net:5044)): EOF
logstash is configured with SSL certificate.
I am able to send message without TLS enabled.

Any suggestion is appreciated.
This is also frustrating not getting proper message from filebeat.
Seems not user friendly

[rugenl (Len Rugen)]

You're not giving us much to work with, but try the filebeat output option verification_mode: none

If that works, you have a certificate issue. If it still doesn't work, post your logstash input and filebeat configs.

[NetRajan (Rajan Bhatt)]

Hi Ren
Thanks for your input. Appreciate your insight in resolving it. As mentioned this works if SSL is not enabled for logstash. Seems something is not right about our certificate. SSL is very important to us, so I really want to solve it. Thanks in advance

I tried to use verification_mode:none but did not help as indicated below.

2020-06-08T09:03:48.940-0700	ERROR	pipeline/output.go:100	Failed to connect to backoff(async(tcp://logstash-xxx.devero.net:5044)): EOF
2020-06-08T09:03:48.940-0700	INFO	pipeline/output.go:93	Attempting to reconnect to backoff(async(tcp://logstash.xxxnet:5044)) with 4 reconnect attempt(s)

This is filebeat.yml file

filebeat.inputs:

Each - is an input. Most options can be set at the input level, so

you can use different inputs for various configurations.

Below are the input specific configurations.

• type: log

  Change to true to enable this input configuration.

  enabled: true

  Paths that should be crawled and fetched. Glob based paths.

  paths:

  • /tmp/myfilebeat.log

  - /var/log/*.log

  #- c:\programdata\elasticsearch\logs*

Exclude lines. A list of regular expressions to match. It drops the lines that are

matching any regular expression from the list.

#exclude_lines: ['^DBG']

Include lines. A list of regular expressions to match. It exports the lines that are

matching any regular expression from the list.

#include_lines: ['^ERR', '^WARN']

Exclude files. A list of regular expressions to match. Filebeat drops the files that

are matching any regular expression from the list. By default, no files are dropped.

#exclude_files: ['.gz$']

Optional additional fields. These fields can be freely picked

to add additional information to the crawled log files for filtering

#fields:

level: debug

review: 1

Multiline options

Multiline can be used for log messages spanning multiple lines. This is common

for Java Stack Traces or C-Line Continuation

The regexp Pattern that has to be matched. The example pattern matches all lines starting with [

#multiline.pattern: ^[

Defines if the pattern set under pattern should be negated or not. Default is false.

#multiline.negate: false

Match can be set to "after" or "before". It is used to define if lines should be append to a pattern

that was (not) matched before or after or as long as a pattern is not matched based on negate.

Note: After is the equivalent to previous and before is the equivalent to to next in Logstash

#multiline.match: after

#============================= Filebeat modules ===============================

filebeat.config.modules:

Glob pattern for configuration loading

path: ${path.config}/modules.d/*.yml

Set to true to enable config reloading

reload.enabled: false

#==================== Elasticsearch template setting ==========================

setup.template.settings:

index.number_of_shards: 1

#index.codec: best_compression

#_source.enabled: false

#================================ General =====================================

The name of the shipper that publishes the network data. It can be used to group

all the transactions sent by a single shipper in the web interface.

#name:

The tags of the shipper are included in their own field with each

transaction published.

#tags: ["service-X", "web-tier"]

Optional fields that you can specify to add additional information to the

output.

#fields:

env: staging

#============================== Dashboards =====================================

These settings control loading the sample dashboards to the Kibana index. Loading

the dashboards is disabled by default and can be enabled either by setting the

options here or by using the setup command.

#setup.dashboards.enabled: false

The URL from where to download the dashboards archive. By default this URL

has a value which is computed based on the Beat name and version. For released

versions, this URL points to the dashboard archive on the artifacts.elastic.co

website.

#setup.dashboards.url:

#============================== Kibana =====================================

Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

This requires a Kibana endpoint configuration.

setup.kibana:

Kibana Host

Scheme and port can be left out and will be set to the default (http and 5601)

In case you specify and additional path, the scheme is required: http://localhost:5601/path

IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

#host: "localhost:5601"

Kibana Space ID

ID of the Kibana Space into which the dashboards should be loaded. By default,

#============================= Elastic Cloud ==================================

These settings simplify using Filebeat with the Elastic Cloud (https://cloud.elastic.co/).

The cloud.id setting overwrites the output.elasticsearch.hosts and

setup.kibana.host options.

You can find the cloud.id in the Elastic Cloud web UI.

#cloud.id:

The cloud.auth setting overwrites the output.elasticsearch.username and

output.elasticsearch.password settings. The format is <user>:<pass>.

#cloud.auth:

#================================ Outputs =====================================

Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------

output.elasticsearch:

Array of hosts to connect to.

hosts: ["localhost:9200"]

Protocol - either http (default) or https.

#protocol: "https"

Authentication credentials - either API key or username/password.

#api_key: "id:api_key"
#username: "elastic"

#----------------------------- Logstash output --------------------------------
output.logstash:

The Logstash hosts

hosts: ["logstash.xxx.net:5044"]

Optional SSL. By default is off.

List of root certificates for HTTPS server verifications

ssl.certificate_authorities: ["/Users/xxxx/filebeat-7.6.2-darwin-x86_64/logstash.crt"]
verification_mode: none

Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

#================================ Processors =====================================

Configure processors to enhance or manipulate events generated by the beat.

#================================ Processors =====================================

Configure processors to enhance or manipulate events generated by the beat.

processors:

• add_host_metadata: ~

• add_cloud_metadata: ~

• add_docker_metadata: ~

• add_kubernetes_metadata: ~

#================================ Logging =====================================

Sets log level. The default log level is info.

Available log levels are: error, warning, info, debug

#logging.level: debug

At debug level, you can selectively enable logging only for some components.

To enable all selectors use ["*"]. Examples of other selectors are "beat",

"publish", "service".

#logging.selectors: ["*"]

#============================== X-Pack Monitoring ===============================

filebeat can export internal metrics to a central Elasticsearch monitoring

cluster. This requires xpack monitoring to be enabled in Elasticsearch. The

reporting is disabled by default.

Set to true to enable the monitoring reporter.

#monitoring.enabled: false

Sets the UUID of the Elasticsearch cluster under which monitoring data for this

Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch

is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.

#monitoring.cluster_uuid:

Uncomment to send the metrics to Elasticsearch. Most settings from the

Elasticsearch output are accepted here as well.

Note that the settings should point to your Elasticsearch monitoring cluster.

Any setting that is not set is automatically inherited from the Elasticsearch

output configuration, so if you have the Elasticsearch output configured such

that it is pointing to your Elasticsearch monitoring cluster, you can simply

uncomment the following line.

#monitoring.elasticsearch:

#================================= Migration ==================================

This allows to enable 6.7 migration aliases

#migration.6_to_7.enabled: true

==== Filebeat.yml ends --

Logstash conf file

input {
beats {
codec => json
port => 5044
ssl_certificate => "/etc/logstash/ssl/logstash_filebeats_self_signed.crt"
ssl_key => "/etc/logstash/logstash_filebeats_self_signed.key"
}
s3 {
"type" => "mobile"
"region" => "us-west-2"
"bucket" => "xyzw-mobile"
"prefix" => "offline-logs/"
"codec" => "json"
}
tcp {
codec => json
port => 10514
ssl_enable => false
ssl_verify => false
type => "log4j-json"
}
}

filter {
if [type] == "mobile" {
date {
match => ["[timestamp]", "UNIX_MS"]
target => "@timestamp"
}
fingerprint {
key => "secret"
method => "SHA256"
concatenate_sources => "true"
source => ["chunkId", "@timestamp"]
target => "[@metadata][fingerprint]"
remove_field=>["chunkId", "timestamp"]
}
}
else {
json {
source => "message"
}
}
}
output {
if [type] == "mobile" {
elasticsearch {
hosts => [ "search:443" ]
document_id => "%{[@metadata][fingerprint]}"
document_type => "log4j-json"
ssl => true
flush_size => 250000
}
}
else {
if [type] == "log" {
elasticsearch {
hosts => [ "search:443" ]
document_type => "log4j-json"
ssl => true
flush_size => 250000
}
}
else {
elasticsearch {
hosts => [ "search:443" ]
ssl => true
flush_size => 250000
}
}
}
}

==== end of logstash.conf ==

[rugenl (Len Rugen)]

Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

Those options are comments, unless they were corrupted when pasted into the forum.

[NetRajan (Rajan Bhatt)]

They are commented. We only do server authentication.
Hope that is what you are asking
Please let me know