Filebeat to Logstash error wsarecv

I'm running beat on windows server 2012 and ELK stack on Ubuntu 16. I have checked the firewall and port 5044 is open, telnet also proves the same.

Logstash.conf

input {
  beats {
    port => 5044
  }
}

output {
  elasticsearch {
    hosts => ["http://localhost:9200"]
    index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
    document_type => "%{[@metadata][type]}"
  }
}

beat.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:
    - C:\Program Files (x86)\PrivateArk\Server\ita*
    #- 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 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: [""]

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

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

Beat log file:

2017-03-10T14:45:09-06:00 ERR Connecting error publishing events (retrying): Get http://10.0.0.12:5044: read tcp 10.0.0.10:49784->10.0.0.12:5044: wsarecv: An existing connection was forcibly closed by the remote host. 2017-03-10T14:45:32-06:00 INFO Non-zero metrics in the last 30s: libbeat.es.publish.write_bytes=121 libbeat.es.publish.read_errors=1 2017-03-10T14:45:41-06:00 ERR Connecting error publishing events (retrying): Get http://10.0.0.12:5044: read tcp 10.0.0.10:49785->10.0.0.12:5044: wsarecv: An existing connection was forcibly closed by the remote host. 2017-03-10T14:46:02-06:00 INFO Non-zero metrics in the last 30s: libbeat.es.publish.write_bytes=121 libbeat.es.publish.read_errors=1 2017-03-10T14:46:32-06:00 INFO No non-zero metrics in the last 30s 2017-03-10T14:46:41-06:00 ERR Connecting error publishing events (retrying): Get http://10.0.0.12:5044: read tcp 10.0.0.10:49788->10.0.0.12:5044: wsarecv: An existing connection was forcibly closed by the remote host. 2017-03-10T14:47:02-06:00 INFO Non-zero metrics in the last 30s: libbeat.es.publish.read_errors=1 libbeat.es.publish.write_bytes=121 2017-03-10T14:47:32-06:00 INFO No non-zero metrics in the last 30s

Any thoughts?

Logstash isn't listening on the port 5044

You are using the elasticsearch output which is probably why it is having problems.

Comment out the output.elasticsearch options in the config file. And uncomment the output.logstash options.

1 Like

That was the issue.
Thanks.

It is working now, is there a reason why I see duplicate indices?

The reason is because you had two outputs before. In the future you should see only the logstash one.

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