# Start es cluster ,the health status is red

**URL:** https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947
**Category:** Elasticsearch
**Created:** [March 17, 2017, 1:05am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947 "2017-03-17T01:05:55Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![hexian55](https://avatars.discourse-cdn.com/v4/letter/h/f07891/32.png) [@hexian55](https://discuss.elastic.co/u/hexian55)
#### Post date: [March 17, 2017, 1:05am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947/1 "2017-03-17T01:05:56Z")

</div>

Elasticsearch version:  
5.2.1  
Plugins installed: []

JVM version:  
jdk:1.8.0\_111  
OS version:  
centos7.0

configuration file as follows  
[cluster.name](http://cluster.name): tj-es-staging  
node.master: true  
node.data: true  
[node.name](http://node.name): ${HOSTNAME}  
network.host: ${HOSTNAME}  
http.port: 9200  
path.data: /home/work/data1/data/es\_data  
path.logs: /home/work/log/es\_log

discovery.zen.minimum\_master\_nodes: 1  
discovery.zen.ping\_timeout: 100s  
discovery.zen.fd.ping\_timeout: 100s  
discovery.zen.ping.unicast.hosts: ["10...."]  
#es head  
http.cors.enabled: true  
http.cors.allow-origin: "\*"

gateway.expected\_nodes: 5  
gateway.recover\_after\_time: 10m  
gateway.recover\_after\_nodes: 4

HI  
when I start my es cluster, the health status always red.  
curl '[http://XXX:9200/\_cluster/health?pretty](http://XXX:9200/_cluster/health?pretty)'  
{  
"cluster\_name" : "tj-es-staging",  
"status" : "red",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 0,  
"number\_of\_in\_flight\_fetch" : 0,  
"task\_max\_waiting\_in\_queue\_millis" : 0,  
"active\_shards\_percent\_as\_number" : "NaN"  
}

curl '[http://XXX:9200/\_cat/indices?v](http://XXX:9200/_cat/indices?v)'  
{"error":{"root\_cause":[{"type":"cluster\_block\_exception","reason":"blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];"}],"type":"cluster\_block\_exception","reason":"blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];"},"status":503}

**I have other es clusters also using a similar configuration file,it's no problem.**  
**I think there may be a problem with my server environment, but reported that the wrong I do not know how to troubleshoot**

the server log  
[2017-03-16T16:46:44,515][INFO][o.e.n.Node] [staging03] initializing ...  
[2017-03-16T16:46:44,582][INFO][o.e.e.NodeEnvironment] [staging03] using [1] data paths, mounts [[/home/work/data1 (/dev/vdb1)]], net usable\_space [934gb], net total\_space [984.1gb], spins? [possibly], types [ext4]  
[2017-03-16T16:46:44,582][INFO][o.e.e.NodeEnvironment] [staging03] heap size [30.8gb], compressed ordinary object pointers [true]  
[2017-03-16T16:46:44,583][INFO][o.e.n.Node] [staging03] node name [staging03], node ID [WxccNuCbTTmyy1lRlApQDA]  
[2017-03-16T16:46:44,585][INFO][o.e.n.Node] [staging03] version[5.2.1], pid[6933], build[db0d481/2017-02-09T22:05:32.386Z], OS[Linux/3.10.0-123.el7.x86\_64/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0\_111/25.111-b14]  
[2017-03-16T16:46:45,237][INFO][o.e.p.PluginsService] [staging03] loaded module [aggs-matrix-stats]  
[2017-03-16T16:46:45,237][INFO][o.e.p.PluginsService] [staging03] loaded module [ingest-common]  
[2017-03-16T16:46:45,237][INFO][o.e.p.PluginsService] [staging03] loaded module [lang-expression]  
[2017-03-16T16:46:45,237][INFO][o.e.p.PluginsService] [staging03] loaded module [lang-groovy]  
[2017-03-16T16:46:45,237][INFO][o.e.p.PluginsService] [staging03] loaded module [lang-mustache]  
[2017-03-16T16:46:45,238][INFO][o.e.p.PluginsService] [staging03] loaded module [lang-painless]  
[2017-03-16T16:46:45,238][INFO][o.e.p.PluginsService] [staging03] loaded module [percolator]  
[2017-03-16T16:46:45,238][INFO][o.e.p.PluginsService] [staging03] loaded module [reindex]  
[2017-03-16T16:46:45,238][INFO][o.e.p.PluginsService] [staging03] loaded module [transport-netty3]  
[2017-03-16T16:46:45,238][INFO][o.e.p.PluginsService] [staging03] loaded module [transport-netty4]  
[2017-03-16T16:46:45,239][INFO][o.e.p.PluginsService] [staging03] no plugins loaded  
[2017-03-16T16:46:47,977][INFO][o.e.n.Node] [staging03] initialized  
[2017-03-16T16:46:47,978][INFO][o.e.n.Node] [staging03] starting ...  
[2017-03-16T16:46:48,189][WARN][i.n.u.i.MacAddressUtil] Failed to find a usable hardware address from the network interfaces; using random bytes: c1:5c:67:35:da:13:34:d9  
[2017-03-16T16:46:48,508][INFO][o.e.t.TransportService] [staging03] publish\_address {xxx:9300}, bound\_addresses {xxx:9300}  
[2017-03-16T16:46:48,513][INFO][o.e.b.BootstrapChecks] [staging03] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks  
[2017-03-16T16:47:18,596][WARN][o.e.n.Node] [staging03] timed out while waiting for initial discovery state - timeout: 30s  
[2017-03-16T16:47:18,606][INFO][o.e.h.HttpServer] [staging03] publish\_address {xxx:9200}, bound\_addresses {xxx:9200}  
[2017-03-16T16:47:18,606][INFO][o.e.n.Node] [staging03] started  
[2017-03-16T16:48:28,661][INFO][o.e.c.s.ClusterService] [staging03] new\_master {staging03}{WxccNuCbTTmyy1lRlApQDA}{VZQBiKQESJ-a8mlYspuHaw}{staging03}{xxx:9300}, reason: zen-disco-elected-as-master ([0] nodes joined)  
[2017-03-16T16:49:41,519][WARN][r.suppressed] path: /\_cat/indices, params: {}  
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE\_UNAVAILABLE/1/state not recovered / initialized];  
at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:165) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.admin.indices.stats.TransportIndicesStatsAction.checkGlobalBlock(TransportIndicesStatsAction.java:70) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.admin.indices.stats.TransportIndicesStatsAction.checkGlobalBlock(TransportIndicesStatsAction.java:47) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction.(TransportBroadcastByNodeAction.java:256) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:234) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction.doExecute(TransportBroadcastByNodeAction.java:79) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:173) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:145) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:87) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.client.node.NodeClient.executeLocally(NodeClient.java:75) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.client.node.NodeClient.doExecute(NodeClient.java:64) ~[elasticsearch-5.2.1.jar:5.2.1]  
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:403) ~[elasticsearch-5.2.1.jar:5.2.1]  
at ....

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 17, 2017, 6:25am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947/2 "2017-03-17T06:25:02Z")

</div>

Please format your code using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21). It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

Why did you add:

```
gateway.expected_nodes: 5
gateway.recover_after_time: 10m
gateway.recover_after_nodes: 4
```

---

<div class="post-metadata">

### Author: ![hexian55](https://avatars.discourse-cdn.com/v4/letter/h/f07891/32.png) [@hexian55](https://discuss.elastic.co/u/hexian55)
#### Post date: [March 17, 2017, 8:07am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947/3 "2017-03-17T08:07:08Z")

</div>

I'm sorry to be too careless

---

<div class="post-metadata">

### Author: ![hexian55](https://avatars.discourse-cdn.com/v4/letter/h/f07891/32.png) [@hexian55](https://discuss.elastic.co/u/hexian55)
#### Post date: [March 17, 2017, 8:19am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947/4 "2017-03-17T08:19:06Z")

</div>

Because my previous cluster is 5 nodes, plus this configuration is to quickly restart, I removed the configuration on the normal, very grateful

---

<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: [April 14, 2017, 8:19am UTC](https://discuss.elastic.co/t/start-es-cluster-the-health-status-is-red/78947/5 "2017-04-14T08:19:11Z")

</div>

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