Winlogbeat disconnects every 10min


(David) #1

Hi !
I have an small issue with an winlogbeat.
It works but unexpectedly it is disconnected somehow evey 10 minutes.
2018-09-20T10:03:29.716+0200 ERROR logstash/async.go:252 Failed to publish events caused by: write tcp xx.xxx.xxx.xx:52716->xxx.xx.xxx.xx:5044: wsasend: An existing connection was forcibly closed by the remote host. 2018-09-20T10:03:29.717+0200 ERROR logstash/async.go:252 Failed to publish events caused by: write tcp xx.xxx.xxx.xx:52717->xxx.xx.xxx.xx:5044: wsasend: An existing connection was forcibly closed by the remote host.

The winlogbeat.yml looks like this:

######### Winlogbeat Configuration Example #########
# This file is an example configuration file highlighting only the most common
# options. The winlogbeat.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/winlogbeat/index.html
#========== Winlogbeat specific options =========
# event_logs specifies a list of event logs to monitor as well as any
# accompanying options. The YAML data type of event_logs is a list of
# dictionaries.
#
# The supported keys are name (required), tags, fields, fields_under_root,
# forwarded, ignore_older, level, event_id, provider, and include_xml. Please
# visit the documentation for the complete details of each option.
# https://go.es.io/WinlogbeatConfig
winlogbeat.event_logs:
    - name: Application
      ignore_older: 5m
    - name: Security
      ignore_older: 5m
    - name: System
      ignore_older: 5m
    - name: DFS Replication
      ignore_older: 5m
    - name: Directory Service
      ignore_older: 5m
    - name: DNS Server
      ignore_older: 5m
    - name: DhcpAdminEvents
      ignore_older: 5m
    - name: Microsoft-Windows-Dhcp-Server/Operational
      ignore_older: 5m
    - name: Microsoft-Windows-AppLocker/EXE and DLL
      ignore_older: 5m
    - name: Microsoft-Windows-AppLocker/MSI and Script
      ignore_older: 5m
    - name: CloudRobot
      ignore_older: 5m
    - name: Veritas Enterprise Vault
      ignore_older: 5m
    - name: Microsoft-Windows-PrintService/Admin
      ignore_older: 5m
#============= Elasticsearch template setting ==================
#setup.template.settings:
  #index.number_of_shards: 3
  #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` CLI flag or 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"
#============= Elastic Cloud ===============
# These settings simplify using winlogbeat 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"]
  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"
#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["xxx.xxx.xxx:5044" , "xxx.xxx.xxx:5044"]
  loadbalance: true
  backoff.init: 30s
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  ssl.certificate_authorities: ["C:/Program Files (x86)/winlogbeat-6.4v1-64-windows/ssl/ca.crt"]
  # Certificate for SSL client authentication
  ssl.certificate: "C:/Program Files (x86)/winlogbeat-6.4v1-64-windows/ssl/xxx.prod.crt"
  # Client Certificate Key
  ssl.key: "C:/Program Files (x86)/winlogbeat-6.4v1-64-windows/ssl/xxx.prod.key"
#================================ Logging =====================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
logging.to_files: true
logging.files: 
  path: C:\Program Files (x86)\winlogbeat-6.4v1-64-windows\Logs
  keepfiles: 2
logging.level: info
# 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: ["*"]
#============= Xpack Monitoring ===============
# winlogbeat 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.
#xpack.monitoring.enabled: false
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well. Any setting that is not set is
# automatically inherited from the Elasticsearch output configuration, so if you
# have the Elasticsearch output configured, you can simply uncomment the
# following line.
#xpack.monitoring.elasticsearch:

I would like to find out why it disconnects all 10 minutes.
Any ideas or help is appreciated.
Thanks in advance David


(ruflin) #2

Often this is cause by something like a load balancer or similar between Logstash and Winlogbeat. Also search on the forum for similar error message as you might find some interesting comments.


(David) #3

Thanks for the answer , i already did search the forums for the perticular error message but in the whole setup there is no loadbalancer or firewall between those machines.

It is a plain test setup with two logstash hosts and two windows machines of which just one winlogbeat shows this strange behaviour.

what we haven't ruled out yet is hardware failure due to a defective nic ...

Regards

David


(system) #4

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