Logstash error in filebeat log

[intsec]

I have both filebeat and metricbeat running on a Windows server and metricbeat sends logs just fine to logstash but filebeat is showing me errors.
Failed to connect to backoff(async(tcp://mymangerip:5044)): dial tcp mymanagerip:5044: connectex: No connection could be made because the target machine actively refused it."

I know firewall rules are good since metricbeat can send just fine. Any help would be appreciated. Thanks!

[dougburks]

Are both filebeat and metricbeat configured to connect to mymangerip:5044?

[intsec]

Yes From: Doug Burks ***@***.***> Sent: Friday, December 2, 2022 12:28 PM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Are both filebeat and metricbeat configured to connect to mymangerip:5044? — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC4PLI22D57L3IS7OJDWLIWQTANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

Have you run tcpdump on your Security Onion management interface to verify that it is actually receiving traffic from both filebeat and metricbeat?

[intsec]

Metricbeat logs are being parsed and seen in Kibana, I don’t however see anything coming in for Filbeat. From: Doug Burks ***@***.***> Sent: Monday, December 5, 2022 7:44 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Have you run tcpdump on your Security Onion management interface to verify that it is actually receiving traffic from both filebeat and metricbeat? — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC23KLNQJOMCFJAV7JTWLXPSBANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

Metricbeat logs are being parsed and seen in Kibana, I don’t however see anything coming in for Filbeat.

Let's take Kibana out of the equation altogether. Have you run tcpdump on your Security Onion management interface to verify that Filebeat traffic is actually reaching the interface? You could stop metricbeat and only run Filebeat and then see if any traffic is arriving at port 5044.

[intsec]

I also am seeing this in the logstash logs. ][WARN ][io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. java.net.SocketException: Connection reset Researching this people are saying I have SSL enabled in my config file which I do not. From: Doug Burks ***@***.***> Sent: Monday, December 5, 2022 7:44 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Have you run tcpdump on your Security Onion management interface to verify that it is actually receiving traffic from both filebeat and metricbeat? — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC23KLNQJOMCFJAV7JTWLXPSBANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[intsec]

Yes, I have ran tcpdump on my manager and am seeing it communicate but every little bit it sends a reset. I have turned off Metricbeat and even uninstalled it. From: Doug Burks ***@***.***> Sent: Tuesday, December 6, 2022 2:18 PM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Metricbeat logs are being parsed and seen in Kibana, I don’t however see anything coming in for Filbeat. Let's take Kibana out of the equation altogether. Have you run tcpdump on your Security Onion management interface to verify that Filebeat traffic is actually reaching the interface? You could stop metricbeat and only run Filebeat and then see if any traffic is arriving at port 5044. — Reply to this email directly, view it on GitHub<#9262 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC3ZCRMX2A3U7ZXMGO3WL6GPHANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

Have you verified that the version number of filebeat and metricbeat match the version of the Elastic stack?

[intsec]

Yes, both are 8.4.3 OSS. From: Doug Burks ***@***.***> Sent: Wednesday, December 7, 2022 1:08 PM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Have you verified that the version number of filebeat and metricbeat match the version of the Elastic stack? — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC25J6JC4X5MF4XPCQTWMDHA7ANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

Are there any other clues in filebeat's diagnostic log?

[intsec]

Yes, the only thing that it tells me is what I mentioned in my original message for this post. From: Doug Burks ***@***.***> Sent: Friday, December 9, 2022 7:33 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Have you checked filebeat's diagnostic log for additional clues? — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUCZOCGFQVJ7TKJWFJUTWMMRGTANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

The next thing I would try is downloading a fresh copy of Filebeat (making sure the version number matches) and starting from a fresh configuration to see if that makes any difference.

[intsec]

I have done this already. This makes no sense, thanks for any help Doug, I appreciate it. Eric From: Doug Burks ***@***.***> Sent: Monday, December 12, 2022 7:11 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) The next thing I would try is downloading a fresh copy of Filebeat (making sure the version number matches) and starting from a fresh configuration to see if that makes any difference. — Reply to this email directly, view it on GitHub<#9262 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC4SOCJGYYBV63AWJSDWM4I47ANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

Are you able to share your Filebeat configuration?

[intsec]

###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

# ============================== Filebeat inputs ===============================

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.

# filestream is an input for collecting log messages from files.
- type: filestream

  # Unique ID among all inputs, an ID is required.
  id: my-filestream-id

  # Change to true to enable this input configuration.
  enabled: false

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    # - /var/log/*.log
    - C:\ProgramData\Elastic\Beats\filebeat\logs\*

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #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.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #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.
  #prospector.scanner.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

# ============================== 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

  # Period on which files under path should be checked for changes
  #reload.period: 10s

# ======================= 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,
  # the Default Space will be used.
  #space.id:

# =============================== 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"
  #password: "changeme"

# ------------------------------ Logstash Output -------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["intsec-ids:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

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

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

# ================================= Processors =================================
processors:
  - add_host_metadata:
      when.not.contains.tags: forwarded
  - 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",
# "publisher", "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:

# ============================== Instrumentation ===============================

# Instrumentation support for the filebeat.
#instrumentation:
    # Set to true to enable instrumentation of filebeat.
    #enabled: false

    # Environment in which filebeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    #  - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:


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

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

[dougburks]

Have you tried commenting out the setup.kibana section to see if that makes any difference?

Have you tried increasing logging.level to look for additional clues?

[intsec]

I have not tried either. I will test that. Thanks! From: Doug Burks ***@***.***> Sent: Thursday, December 15, 2022 7:29 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Have you tried commenting out the setup.kibana section to see if that makes any difference? Have you tried increasing logging.level to look for additional clues? — Reply to this email directly, view it on GitHub<#9262 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUC323ZDDE5I2RUMU6DLWNMFJPANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[intsec]

I commented out Kibana and turned on debugging logging. Still having issues I am seeing a new message ""message":"handle error: write tcp 1.1.1.1:34324->2.2.2.2:5044: write: connection reset by peer" Oh and I thought this was on just a Windows box but it's also doing this on one of my Linux boxes as well. Any server running filebeat does this, but Metricbeat and Auditbeat sending to Logstash does not and works just fine.

[dougburks]

Is the traffic going through any kind of network inspection device that might be interfering with the traffic?

[intsec]

No and if it was that doesn’t explain how metricbeat works. Thanks again Doug! From: Doug Burks ***@***.***> Sent: Friday, January 6, 2023 7:22 AM To: Security-Onion-Solutions/securityonion ***@***.***> Cc: Eric Vanderveer ***@***.***>; Author ***@***.***> Subject: Re: [Security-Onion-Solutions/securityonion] Logstash error in filebeat log (Discussion #9262) Is the traffic going through any kind of network inspection device that might be interfering with the traffic? — Reply to this email directly, view it on GitHub<#9262 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLMUCYX2ZZHYWO6HZVUJBLWRAE7FANCNFSM6AAAAAASQ7VROI>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dougburks]

If I were you, I would set up a fresh installation of Security Onion (perhaps in a VM) and then set up a fresh filebeat installation (perhaps in a second VM), verify everything works correctly there, and then compare the working deployment with the non-working deployment to try to pinpoint where the issue is.