# Elasticsearch \_cluster/health shows as red
**URL:** https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756
**Category:** Elasticsearch
**Created:** [April 12, 2018, 7:59am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756 "2018-04-12T07:59:07Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@harika.gudumasu](https://discuss.elastic.co/u/harika.gudumasu)
#### Post date: [April 12, 2018, 7:59am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756/1 "2018-04-12T07:59:07Z")
Hello,
I am new to elasticsearch and trying to start in one node. It says as below.
[2018-04-12T08:45:55,908][INFO][o.e.c.s.ClusterApplierService] [lonrs11800] new\_master {lonrs11800}{YF-Mz0X1TcWrKsmEHwMrLQ}{a-BLHg\_qTOKkrI2AzPPO1A}{localhost}{127.0.0.1:9300}{rack=r1}, reason: apply cluster state (from master [master {lonrs11800}{YF-Mz0X1TcWrKsmEHwMrLQ}{a-BLHg\_qTOKkrI2AzPPO1A}{localhost}{127.0.0.1:9300}{rack=r1} committed version [1] source [zen-disco-elected-as-master ([0] nodes joined)]]
which shows no master nodes joined and health status shows as read. Please find my config file as below. Please help in fixing the same
cat elasticsearch.yml
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# [https://www.elastic.co/guide/en/elasticsearch/reference/index.html](https://www.elastic.co/guide/en/elasticsearch/reference/index.html)
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: MWBW\_GMH\_DEV
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: lonrs11819
node.master: true
node.data: false
#
# Add custom attributes to the node:
#
node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: /opt/app/tibco/install/elasticsearch/data
#
# Path to log files:
#
path.logs: /opt/app/tibco/install/elasticsearch/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
bootstrap.memory\_lock: true
bootstrap.system\_call\_filter: false
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: "11.195.97.65"
transport.host: localhost
network.publish\_host: "11.195.97.65"
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
discovery.zen.minimum\_master\_nodes: 1
discovery.zen.ping.unicast.hosts: "11.195.97.65"
discovery.zen.no\_master\_block: write
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
gateway.recover\_after\_nodes: 10
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
action.destructive\_requires\_name: true
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [April 13, 2018, 2:57pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756/2 "2018-04-13T14:57:18Z")
If you are new to Elasticsearch, I would recommend you start by running node with default settings.
> [@harika.gudumasu](#):
>
> node.data: false
Every cluster need at least one data node, so you are not going to get very far with your current configuration.
> [@harika.gudumasu](#):
>
> gateway.recover\_after\_nodes: 10
Why have you set this if you only have 1 node?
---
### Author:  [@harika.gudumasu](https://discuss.elastic.co/u/harika.gudumasu)
#### Post date: [April 16, 2018, 6:37am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756/3 "2018-04-16T06:37:47Z")
Hi Christian,
I am able to run Elasticsearch and Kibana successfully without any errors now.
Trying to start filebeat wherein facing the below error. Could you please help in resolving the same.
(UAT) bwadmind@lonrs11800$ ./filebeat -e -c filebeat.yml -d "publish"
2018-04-16T07:21:43.346+0100 INFO instance/beat.go:468 Home path: [/opt/app/tibco/install/filebeat-6.2.2-linux-x86\_64] Config path: [/opt/app/tibco/install/filebeat-6.2.2-linux-x86\_64] Data path: [/opt/app/tibco/install/filebeat-6.2.2-linux-x86\_64/data] Logs path: [/opt/app/tibco/install/filebeat-6.2.2-linux-x86\_64/logs]
2018-04-16T07:21:43.346+0100 DEBUG [beat] instance/beat.go:495 Beat metadata path: /opt/app/tibco/install/filebeat-6.2.2-linux-x86\_64/data/meta.json
2018-04-16T07:21:43.346+0100 INFO instance/beat.go:475 Beat UUID: 93ef441f-8b74-445a-a0ca-48bba25b7ca1
2018-04-16T07:21:43.346+0100 INFO instance/beat.go:213 Setup Beat: filebeat; Version: 6.2.2
2018-04-16T07:21:43.346+0100 DEBUG [beat] instance/beat.go:230 Initializing output plugins
2018-04-16T07:21:43.346+0100 DEBUG [processors] processors/processor.go:49 Processors:
2018-04-16T07:21:43.347+0100 INFO elasticsearch/client.go:145 Elasticsearch url: [http://lonrs11800:9200](http://lonrs11800:9200)
2018-04-16T07:21:43.347+0100 INFO pipeline/module.go:76 Beat name: logs
2018-04-16T07:21:43.347+0100 INFO [monitoring] log/log.go:97 Starting metrics logging every 30s
2018-04-16T07:21:43.347+0100 INFO elasticsearch/client.go:145 Elasticsearch url: [http://lonrs11800:9200](http://lonrs11800:9200)
2018-04-16T07:21:43.348+0100 DEBUG [elasticsearch] elasticsearch/client.go:666 ES Ping(url=http://lonrs11800:9200)
2018-04-16T07:21:43.349+0100 DEBUG [elasticsearch] elasticsearch/client.go:689 Ping status code: 200
2018-04-16T07:21:43.349+0100 INFO elasticsearch/client.go:690 Connected to Elasticsearch version 6.2.2
2018-04-16T07:21:43.349+0100 DEBUG [dashboards] dashboards/es\_loader.go:309 Initialize the Elasticsearch 6.2.2 loader
2018-04-16T07:21:43.349+0100 DEBUG [dashboards] dashboards/es\_loader.go:309 Elasticsearch URL [http://lonrs11800:9200](http://lonrs11800:9200)
2018-04-16T07:21:43.349+0100 INFO kibana/client.go:69 Kibana url: [http://lonrs11800:5601](http://lonrs11800:5601)
2018-04-16T07:21:43.353+0100 DEBUG [dashboards] dashboards/kibana\_loader.go:103 Initialize the Kibana 6.2.2 loader
2018-04-16T07:21:43.353+0100 DEBUG [dashboards] dashboards/kibana\_loader.go:103 Kibana URL [http://lonrs11800:5601](http://lonrs11800:5601)
2018-04-16T07:21:43.353+0100 DEBUG [dashboards] dashboards/kibana\_loader.go:103 Created temporary directory /tmp/tmp995820058
2018-04-16T07:21:43.353+0100 DEBUG [dashboards] dashboards/kibana\_loader.go:103 Downloading [http://lonrs11800:5601](http://lonrs11800:5601)
2018-04-16T07:21:43.355+0100 DEBUG [dashboards] dashboards/kibana\_loader.go:103 Unzip archive /tmp/tmp995820058
2018-04-16T07:21:43.357+0100 INFO [monitoring] log/log.go:132 Total non-zero metrics {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":0,"time":9},"total":{"ticks":0,"time":17,"value":0},"user":{"ticks":0,"time":8}},"info":{"ephemeral\_id":"bd5699de-3370-4351-a322-84b55920054b","uptime":{"ms":17}},"memstats":{"gc\_next":4473924,"memory\_alloc":3108976,"memory\_total":3108976,"rss":13049856}},"filebeat":{"harvester":{"open\_files":0,"running":0}},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"elasticsearch"},"pipeline":{"clients":0,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"cpu":{"cores":2},"load":{"1":0.14,"15":0.04,"5":0.14,"norm":{"1":0.07,"15":0.02,"5":0.07}}}}}}
2018-04-16T07:21:43.357+0100 INFO [monitoring] log/log.go:133 Uptime: 18.22409ms
2018-04-16T07:21:43.357+0100 INFO [monitoring] log/log.go:110 Stopping metrics logging.
2018-04-16T07:21:43.357+0100 ERROR instance/beat.go:667 Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing URL/file: Failed to unzip the archive: /tmp/tmp995820058/lonrs11800:5601: zip: not a valid zip file
Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing URL/file: Failed to unzip the archive: /tmp/tmp995820058/lonrs11800:5601: zip: not a valid zip file
Please find filbeat.yml file as below.
(UAT) bwadmind@lonrs11800$ cat filebeat.yml
###################### 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.
---
### Author:  [@harika.gudumasu](https://discuss.elastic.co/u/harika.gudumasu)
#### Post date: [April 16, 2018, 7:05am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756/4 "2018-04-16T07:05:12Z")
I have got this resolved as well. Thanks for your help.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 14, 2018, 7:05am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-health-shows-as-red/127756/5 "2018-05-14T07:05:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.