Filebeat to Logstash Error publishing events


(Pavanssetty) #1

I'm running filebeat and logstash on windows server 2012. I am constantly seeing below error messages in the Filebeat log. I guess my filebeat is not able to publish all records to logstash as I can see some records in ES.

Error message:

2018-02-15T17:58:23+01:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.publish.read_bytes=6 libbeat.logstash.publish.write_bytes=7401
2018-02-15T17:58:24+01:00 ERR Failed to publish events caused by: read tcp [::1]:57686->[::1]:5044: i/o timeout
2018-02-15T17:58:24+01:00 INFO Error publishing events (retrying): read tcp [::1]:57686->[::1]:5044: i/o timeout
2018-02-15T17:58:53+01:00 INFO Non-zero metrics in the last 30s: libbeat.logstash.call_count.PublishEvents=1 libbeat.logstash.publish.read_errors=1 libbeat.logstash.publish.write_bytes=3913 libbeat.logstash.published_and_acked_events=382 libbeat.logstash.published_but_not_acked_events=1290
2018-02-15T17:58:55+01:00 ERR Failed to publish events caused by: read tcp 127.0.0.1:57911->127.0.0.1:5044: i/o timeout
2018-02-15T17:58:55+01:00 INFO Error publishing events (retrying): read tcp 127.0.0.1:57911->127.0.0.1:5044: i/o timeout
2018-02-15T17:59:09+01:00 ERR Failed to publish events caused by: write tcp 127.0.0.1:57991->127.0.0.1:5044: wsasend: An existing connection was forcibly closed by the remote host.
2018-02-15T17:59:09+01:00 INFO Error publishing events (retrying): write tcp 127.0.0.1:57991->127.0.0.1:5044: wsasend: An existing connection was forcibly closed by the remote host.

filebeat.yml

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

# This file is an example configuration file highlighting only the most common
# options. The filebeat.full.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

#=========================== Filebeat prospectors =============================

filebeat.prospectors:

# Each - is a prospector. Most options can be set at the prospector level, so
# you can use different prospectors for various configurations.
# Below are the prospector specific configurations.

- input_type: log

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    #- /var/log/*.log
    - \\dcgfs-hza-test\DCWorkflowsroottest\.xyz\audit\dcgfs-hza-test\*\*.csv
   
    
  scan_frequency: 30s

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.

  # 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 field can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

  ### Multiline options

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


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

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

# Configure what outputs to use when sending the data collected by the beat.
# Multiple outputs may be used.

#-------------------------- Elasticsearch output ------------------------------
#output.elasticsearch:
  # Array of hosts to connect to.
  #hosts: ["localhost:9200"]

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["localhost: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"

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

# Sets log level. The default log level is info.
# Available log levels are: critical, error, warning, info, debug
logging.level: info
logging.to_files: true
logging.files:
  path: C:\Program Files\Filebeat\logs
  name: filebeat.log
  keepfiles: 7
# 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: ["*"]

logstash.conf

input {
   
    beats {
    port => "5044"
  }
}

I have read through some of the forum discussions on the same topic but could not solve the problem at hand.


(Noémi Ványi) #2

Could you share the full debug logs of Filebeat?
Are you sure there is not any data congestion in Logstash? Is it ready to receive events?


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.