# Elastic server not running after server reboot. i don't know why

**URL:** <https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798>\
**Category:** Elasticsearch\
**Created:** [November 15, 2018, 7:10am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798 "2018-11-15T07:10:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ksb304](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@ksb304](https://discuss.elastic.co/u/ksb304)\
**Post date:** [November 15, 2018, 7:10am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/1 "2018-11-15T07:10:10Z")

</div>

> \*\*elastic \*\*

[2018-11-15T16:04:13,149][DEBUG][o.e.a.s.TransportSearchAction] [cloudoc1] All shards failed for phase: [query]  
[2018-11-15T16:04:13,180][WARN][r.suppressed] path: /.kibana/\_search, params: {ignore\_unavailable=true, index=.kibana, filter\_path=aggregations.types.buckets}  
org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed  
at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseFailure(AbstractSearchAsyncAction.java:293) ~[elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.action.search.AbstractSearchAsyncAction.executeNextPhase(AbstractSearchAsyncAction.java:133) ~[elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.action.search.AbstractSearchAsyncAction.onPhaseDone(AbstractSearchAsyncAction.java:254) ~[elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.action.search.InitialSearchPhase.onShardFailure(InitialSearchPhase.java:101) ~[elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.action.search.InitialSearchPhase.lambda$performPhaseOnShard$1(InitialSearchPhase.java:210) ~[elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.action.search.InitialSearchPhase$1.doRun(InitialSearchPhase.java:189) [elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:723) [elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:41) [elasticsearch-6.4.2.jar:6.4.2]  
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-6.4.2.jar:6.4.2]  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0\_111]  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0\_111]  
at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_111]

> \*\* kibana \*\*

[07:06:03.404] [warning][stats-collection] [search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana/\_search","query":{"ignore\_unavailable":true,"filter\_path":"aggregations.types.buckets"},"body":"{"size":0,"query":{"terms":{"type":["dashboard","visualization","search","index-pattern","graph-workspace","timelion-sheet"]}},"aggs":{"types":{"terms":{"field":"type","size":6}}}}","statusCode":503,"response":"{"error":{"root\_cause":,"type":"search\_phase\_execution\_exception","reason":"all shards failed","phase":"query","grouped":true,"failed\_shards":},"status":503}"}  
at respond (C:\Users\Administrator\Desktop\kibana01\node\_modules\elasticsearch\src\lib\transport.js:307:15)  
at checkRespForFailure (C:\Users\Administrator\Desktop\kibana01\node\_modules\elasticsearch\src\lib\transport.js:266:7)  
at HttpConnector. (C:\Users\Administrator\Desktop\kibana01\node\_modules\elasticsearch\src\lib\connectors\http.js:159:7)  
at IncomingMessage.bound (C:\Users\Administrator\Desktop\kibana01\node\_modules\elasticsearch\node\_modules\lodash\dist\lodash.js:729:21)  
at emitNone (events.js:111:20)  
at IncomingMessage.emit (events.js:208:7)  
at endReadableNT (\_stream\_readable.js:1064:12)  
at \_combinedTickCallback (internal/process/next\_tick.js:138:11)  
at process.\_tickDomainCallback (internal/process/next\_tick.js:218:9)  
log [07:06:03.404] [warning][stats-collection] Unable to fetch data from kibana collector

> \*\* elasticsearch.yml \*\*  
> cluster.name: cloudocCluster  
> node.name: cloudoc1  
> network.host: 192.168.1.99  
> http.port: 9200

> \*\* kibana.yml \*\*  
> server.host: "192.168.1.99"  
> server.name: "cloudockibana"  
> elasticsearch.url: "[http://192.168.1.99:9200](http://192.168.1.99:9200)"

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/9/1903a5de2db915889855b3c2150c385a69fff7d0.png)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 15, 2018, 7:26am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/2 "2018-11-15T07:26:12Z")

</div>

What does the output from `_cat/health` show?

---

<div class="post-metadata">

**Author:** ![ksb304](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@ksb304](https://discuss.elastic.co/u/ksb304)\
**Post date:** [November 15, 2018, 7:34am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/3 "2018-11-15T07:34:20Z")

</div>

![image](https://us1.discourse-cdn.com/elastic/original/3X/7/b/7be1f2e621cd1419c00437d69f2cf3e6ecc86796.png)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 15, 2018, 7:34am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/4 "2018-11-15T07:34:34Z")

</div>

Please don't post pictures of text, they are difficult to read and some people may not be even able to see them.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 15, 2018, 7:37am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/5 "2018-11-15T07:37:00Z")

</div>

You have far too many shards for a cluster that size. Please read [this blog post on shards and sharding](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster) and try to reduce that significantly, e.g. by reindexing into fewer larger indices.

---

<div class="post-metadata">

**Author:** ![ksb304](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@ksb304](https://discuss.elastic.co/u/ksb304)\
**Post date:** [November 15, 2018, 7:37am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/6 "2018-11-15T07:37:48Z")

</div>

> ```
> epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
> 1542267197 16:33:17 cloudocCluster red 1 1 1296 1296 0 4 9285 8 3.1s 12.2%
> 
> ```

> ```
> ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
> 192.168.1.99 33 68 71 mdi * cloudoc1
> 
> ```

---

<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:** [December 13, 2018, 7:38am UTC](https://discuss.elastic.co/t/elastic-server-not-running-after-server-reboot-i-dont-know-why/156798/7 "2018-12-13T07:38:02Z")

</div>

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