# I see this error in logstash-plain.log

**URL:** <https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082>\
**Category:** Elasticsearch\
**Created:** [September 28, 2023, 4:02pm UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082 "2023-09-28T16:02:32Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [September 29, 2023, 11:48am UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082/21 "2023-09-29T11:48:44Z")

</div>

> message=\>"Expected one of [\t\r\n], "#", "=\>" at line 22, column 17 (byte 375) after output {\n elasticsearch {\n hosts =\> ["[https://localhost:9200](https://localhost:9200)"]\n index =\> "%{[@metadata][beat]}-%{+YYYY.MM.dd}"\n ssl\_enabled ",  
> Should be something like this:

```auto
output {
 elasticsearch {
    hosts => ["https://localhost:9200"]
    index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
    user => "elastic"
    password => "fjdjfjdfjdhhfdjhfdjdsfjdhjie"
    ssl_enabled => true
    ssl_verification_mode => "none"
  }
}

```

---

<div class="post-metadata">

**Author:** ![Mostafa\_Faridi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafa_faridi/32/121792_2.png) [@Mostafa\_Faridi](https://discuss.elastic.co/u/Mostafa_Faridi)\
**Post date:** [September 29, 2023, 3:28pm UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082/22 "2023-09-29T15:28:46Z")

</div>

Thanks @Rios and @leandrojmp  
Your guide save my life and right now logstash is running and working  
but I have another problem, I installed filebeat on 6 different servers and want config filebeat send logs to logstash, but in kibana, I only see filebeat logs installed beside elasticsearch and kibana and logstash, but it can not find other filebeat installed on another server.  
this is my filebeat config on other server

```auto
at /etc/filebeat/filebeat.yml
cat: /etc/filebeat/filebeat.yml: Permission denied
[admin@uid_core ~]$ sudo cat /etc/filebeat/filebeat.yml
[sudo] password for admin: 
###################### 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.

- type: log

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    - /home/admin/core/logs/*.log
  json.keys_under_root: true
  json.overwrite_keys: true
    #- 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 fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  # level: debug
  # review: 1

  ### Multiline options

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

# filestream is an experimental input. It is going to replace log input in the future.
- type: log

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    - /home/admin/core/logs/*.log
    #- 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.
  #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: true

  # 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: ["https://192.168.56.79: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",
# "publish", "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

```

and I see this error

```auto
2023-04-09T16:34:07.921+0330	INFO	[beat]	instance/beat.go:997	Host info	{"system_info": {"host": {"architecture":"x86_64","boot_time":"2023-04-02T05:51:42+03:30","containerized":false,"name":"uid_core","ip":["127.0.0.1/8","::1/128","192.168.56.70/26","fe80::250:56ff:feaa:3ccf/64","192.168.122.1/24"],"kernel_version":"3.10.0-1160.83.1.0.1.el7.x86_64","mac":["00:50:56:aa:3c:cf","52:54:00:ed:62:49","52:54:00:ed:62:49"],"os":{"family":"","platform":"ol","name":"Oracle Linux Server","version":"7.9","major":7,"minor":9,"patch":0},"timezone":"+0330","timezone_offset_sec":12600,"id":"039a0f148a6b40d8b004f76c8dbc0422"}}}
2023-04-09T16:34:07.921+0330	INFO	[beat]	instance/beat.go:1026	Process info	{"system_info": {"process": {"capabilities": {"inheritable":null,"permitted":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend"],"effective":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend"],"bounding":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend"],"ambient":null}, "cwd": "/var/log", "exe": "/usr/share/filebeat/bin/filebeat", "name": "filebeat", "pid": 18717, "ppid": 18716, "seccomp": {"mode":"disabled","no_new_privs":false}, "start_time": "2023-04-09T16:34:06.870+0330"}}}
2023-04-09T16:34:07.921+0330	INFO	instance/beat.go:299	Setup Beat: filebeat; Version: 7.10.1
2023-04-09T16:34:07.921+0330	INFO	[index-management]	idxmgmt/std.go:184	Set output.elasticsearch.index to 'filebeat-7.10.1' as ILM is enabled.
2023-04-09T16:34:07.922+0330	INFO	eslegclient/connection.go:99	elasticsearch url: http://192.168.56.79:9200
2023-04-09T16:34:07.922+0330	INFO	[publisher]	pipeline/module.go:113	Beat name: uid_core
2023-04-09T16:34:07.922+0330	INFO	eslegclient/connection.go:99	elasticsearch url: http://192.168.56.79:9200
2023-04-09T16:34:07.923+0330	ERROR	[esclientleg]	eslegclient/connection.go:261	error connecting to Elasticsearch at http://192.168.56.79:9200: Get "http://192.168.56.79:9200": dial tcp 192.168.56.79:9200: connect: connection refused
2023-04-09T16:34:07.923+0330	ERROR	instance/beat.go:956	Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at http://192.168.56.79:9200: Get "http://192.168.56.79:9200": dial tcp 192.168.56.79:9200: connect: connection refused]

```

---

<div class="post-metadata">

**Author:** ![Mostafa\_Faridi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mostafa_faridi/32/121792_2.png) [@Mostafa\_Faridi](https://discuss.elastic.co/u/Mostafa_Faridi)\
**Post date:** [September 30, 2023, 7:47am UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082/23 "2023-09-30T07:47:33Z")

</div>

Any update please

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [September 30, 2023, 10:35am UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082/24 "2023-09-30T10:35:33Z")

</div>

You don't need https for LS, only when you set certs in input/beat.  
Change to:

```auto
output.logstash:
  # The Logstash hosts
  hosts: ["http://192.168.56.79:5044"]

```

When you establish the communication, you can switch to https. Check [the documentation](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-ssl-logstash.html).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 28, 2023, 10:36am UTC](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082/25 "2023-10-28T10:36:14Z")

</div>

Closed on October 28, 2023, 10:36am UTC

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

[Previous page](https://discuss.elastic.co/t/i-see-this-error-in-logstash-plain-log/344082.md?page=1)