Filebeat stopped working post upgrade

Elastic Stack Beats
1

So i migrated filebeat to 5.x from 1.x now am not able to send the logs to logstash.
Filebeat was working perfectly fine with previous version. Now am getting the error

INFO File is inactive: /opt/IBM/WebSphere/AppServer/profiles/DMGRDEV/logs/dmgr/SystemOut.log. Closing because close_inactive of 5m0s reached.
2017-06-07T04:28:04-05:00 INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2017-06-07T04:28:34-05:00 INFO No non-zero metrics in the last 30s
2017-06-07T04:28:38-05:00 ERR Connecting error publishing events (retrying): dial tcp 10.190.188.173:5044: getsockopt: connection refused

I never got this issue with old version.
Am using logstash 2.4 version is it a problem with Filebeat 5.x?

2

Did you have TLS/SSL enabled? The tls settings have been renamed in 5.x release, to match the other elastic products.

3

How do i do that? Could you elaborate more.

4

in case you are using SSL/TLS, you have to rename tls to ssl in the configuration file. Alternatively beats repo contains a script to migrate a configuration file from beats 1.x to 5.x: https://github.com/elastic/beats/blob/master/libbeat/scripts/migrate_beat_config_1_x_to_5_0.py

5

I ran the script this is how my filebeat.yml looks now.

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

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

 - input_type: log
   paths:
    - /opt/IBM/HTTPServer/logs/access_log
   document_type: access_log

 - input_type: log
   paths:
    - /opt/IBM/WebSphere/AppServer/profiles/WPS00/logs/DEV00WPS*/SystemOut.log
    - /opt/IBM/WebSphere/AppServer/profiles/DMGRDEV/logs/dmgr/SystemOut.log
   document_type: BPM

 - input_type: log
   paths:
    - /var/log/messages
    - /var/log/secure
   document_type: syslog

  #- 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"]
 #input_type: log

  # 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
registry_file: /var/lib/filebeat/registry

#================================ 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: ["10.190.188.173: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/tls/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: 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: ["*"]

Below is the logs after the changes

  Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 libbeat.logstash.call_count.PublishEvents=6 libbeat.logstash.publish.read_bytes=36 libbeat.logstash.publish.write_bytes=1824 libbeat.logstash.published_and_acked_events=12 libbeat.publisher.published_events=12 publish.events=13 registrar.states.update=13 registrar.writes=6

    ERR Failed to publish events caused by: read tcp 10.190.119.203:38546->10.190.188.173:5044: i/o timeout
    2017-06-08T04:50:25-05:00 INFO Error publishing events (retrying): read tcp 10.190.119.203:38546->10.190.188.173:5044: i/o timeout
    2017-06-08T04:50:54-05: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=319 libbeat.logstash.published_but_not_acked_events=2
6

So you didn't us SSL/TLS. Have you check logstash logs? The i/o timeout error indicates logstash not sending an ACK in time. In LS 2.x release, LS will not send an ACK if it takes too long or is blocked. In LS 5.4 release, Logstash sends some keep alive signal every few seconds, so filebeat knows LS is still actively processing the batch.

7

Not sure if this is related to this issue,
I am passing --path.settings using below command in logstash after upgrading

/usr/share/logstash/bin/logstash --path.settings=/etc/logstash -t

But when i do configtest as below

/usr/share/logstash/bin/logstash --config.test_and_exit -f /etc/logstash/conf.d/

Getting the warning

 WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults
Could not find log4j2 configuration at path //usr/share/logstash/config/log4j2.properties. Using default config which logs to console
Configuration OK
8

Uhm, no idea about logstash. You think it's not running correctly?

9

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