# Marvel dashboard won't show shards infos

**URL:** <https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [November 25, 2015, 8:04am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525 "2015-11-25T08:04:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vesnica](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@Vesnica](https://discuss.elastic.co/u/Vesnica)\
**Post date:** [November 25, 2015, 8:04am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/1 "2015-11-25T08:04:50Z")

</div>

Elasticsearch 2.1.0 + Kibana 4.3.0 + latest marvel plugins

Sense give me this:

GET \_cat/shards?v

index shard prirep state docs store ip node  
.marvel-es-2015.11.25 0 r STARTED 1556 677kb 172.17.0.1 Charcoal  
.marvel-es-2015.11.25 0 p STARTED 1556 756.8kb 172.17.0.3 MN-E (Ultraverse)  
filebeat-2015.11.25 1 r STARTED 23887 6.1mb 172.17.0.1 Charcoal  
filebeat-2015.11.25 1 p STARTED 23875 6mb 172.17.0.2 Scanner  
filebeat-2015.11.25 4 r STARTED 23656 6mb 172.17.0.1 Charcoal  
filebeat-2015.11.25 4 p STARTED 23633 6mb 172.17.0.2 Scanner  
filebeat-2015.11.25 3 p STARTED 23372 5.9mb 172.17.0.1 Charcoal  
filebeat-2015.11.25 3 r STARTED 23409 6mb 172.17.0.3 MN-E (Ultraverse)  
filebeat-2015.11.25 2 r STARTED 23736 6mb 172.17.0.2 Scanner  
filebeat-2015.11.25 2 p STARTED 23725 6.1mb 172.17.0.3 MN-E (Ultraverse)  
filebeat-2015.11.25 0 p STARTED 23379 5.9mb 172.17.0.1 Charcoal  
filebeat-2015.11.25 0 r STARTED 23398 6mb 172.17.0.3 MN-E (Ultraverse)  
topbeat-2015.11.25 1 p STARTED 9175 2.1mb 172.17.0.1 Charcoal  
topbeat-2015.11.25 1 r STARTED 9175 4.3mb 172.17.0.2 Scanner  
topbeat-2015.11.25 4 p STARTED 8962 2.1mb 172.17.0.1 Charcoal  
topbeat-2015.11.25 4 r STARTED 8962 2.1mb 172.17.0.3 MN-E (Ultraverse)  
topbeat-2015.11.25 3 r STARTED 9099 2mb 172.17.0.1 Charcoal  
topbeat-2015.11.25 3 p STARTED 9099 4.2mb 172.17.0.3 MN-E (Ultraverse)  
topbeat-2015.11.25 2 p STARTED 8963 2.1mb 172.17.0.2 Scanner  
topbeat-2015.11.25 2 r STARTED 8965 2.1mb 172.17.0.3 MN-E (Ultraverse)  
topbeat-2015.11.25 0 r STARTED 8997 2.1mb 172.17.0.2 Scanner  
topbeat-2015.11.25 0 p STARTED 8997 2mb 172.17.0.3 MN-E (Ultraverse)  
.kibana 0 r STARTED 4 30.9kb 172.17.0.1 Charcoal  
.kibana 0 p STARTED 4 30.9kb 172.17.0.2 Scanner  
.marvel-es-data 0 p STARTED 4 3.9kb 172.17.0.2 Scanner  
.marvel-es-data 0 r STARTED 4 3.9kb 172.17.0.3 MN-E (Ultraverse)

Yet Marvel indice dashboard give me this:

filebeat-2015.11.25 (or any other indices)

Status: Not Available  
Documents: N/A  
Data: N/A  
Total Shards: N/A  
Unassigned Shards: N/A

There are no shards allocated.

All things works fine with ES 2.0.0 + Kibana 4.2.1 + marvel plugins.

---

<div class="post-metadata">

**Author:** ![skearns](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skearns/32/125945_2.png) [@skearns](https://discuss.elastic.co/u/skearns)\
**Post date:** [November 25, 2015, 3:41pm UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/2 "2015-11-25T15:41:24Z")

</div>

In Marvel 2.1, we changed our index template a bit. Can you delete the .marvel-es-2015-11-25 index, and see if that does the trick?

---

<div class="post-metadata">

**Author:** ![Vesnica](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@Vesnica](https://discuss.elastic.co/u/Vesnica)\
**Post date:** [November 26, 2015, 12:50am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/3 "2015-11-26T00:50:48Z")

</div>

Dashboard back to normal when I delete the .marvel\* indices and wait for a auto-refresh, but if I reload the page, all shards related info vanished again.

---

<div class="post-metadata">

**Author:** ![Vesnica](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@Vesnica](https://discuss.elastic.co/u/Vesnica)\
**Post date:** [November 26, 2015, 12:53am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/4 "2015-11-26T00:53:02Z")

</div>

Should I update the marvel plugin for ES and KI? and restart them?

Marvel's dashboard show it's version is 2.1.0

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [November 26, 2015, 8:44am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/5 "2015-11-26T08:44:11Z")

</div>

We need to improve the upgrade between 2.0 -\> 2.1...

But for now and if you are OK with deleting some marvel indices then I think that the best to do is:

- check that all the nodes of your cluster are running Elasticsearch 2.1.0 with the latest marvel Agent plugin (2.1.0)
- use Kibana 4.3.0 and the latest Marvel plugin (2.1.0)
- delete the marvel index template (DELETE /\_template/.marvel-es) on your monitoring cluster
- delete the .marvel-es-data and .marvel-es- indices on your monitoring cluster

After few seconds the indices should be created with the latest index template version.

-- Tanguy

---

<div class="post-metadata">

**Author:** ![Vesnica](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@Vesnica](https://discuss.elastic.co/u/Vesnica)\
**Post date:** [November 27, 2015, 1:26am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/6 "2015-11-27T01:26:53Z")

</div>

I'm running ELK stack in docker container, and I will rebuild all the images when new version released.

Dockerfile I wrote is like below:

RUN curl -O [https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/tar/elasticsearch/2.1.0/elasticsearch-2.1.0.tar.gz](https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/tar/elasticsearch/2.1.0/elasticsearch-2.1.0.tar.gz)  
&& tar zxvf elasticsearch-2.1.0.tar.gz   
&& rm elasticsearch-2.1.0.tar.gz   
&& mv elasticsearch-2.1.0 elasticsearch

RUN elasticsearch/bin/plugin   
-DproxyHost=$PROXY\_HOST -DproxyPort=$PROXY\_PORT   
install license

RUN elasticsearch/bin/plugin   
-DproxyHost=$PROXY\_HOST -DproxyPort=$PROXY\_PORT   
install marvel-agent

COPY elasticsearch.yml elasticsearch/config/elasticsearch.yml

ENTRYPOINT ["/home/ubuntu/elasticsearch/bin/elasticsearch"]

EXPOSE 9200 9300

Kibana's Dockerfile is almost identical as above(expect for package name, plugins name and expose), and this mechanism works well when using ES 2.0.0 + Kibana 4.2.0/1

PS: I will destory all old containers before starting the new one, so cluster always started at fresh new state, without any old indices or templates in it.

---

<div class="post-metadata">

**Author:** ![Vesnica](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@Vesnica](https://discuss.elastic.co/u/Vesnica)\
**Post date:** [December 1, 2015, 1:47am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/7 "2015-12-01T01:47:16Z")

</div>

Well, I think I found the reason for it ( but i'm not very sure ): my browser pc didn't reboot for about 2 month, the dashboard can show the shards info correctly after reboot.

I use latest firefox, and the browser's time is synced with server time, so I really can't get why a long running browser will cause this problem.

Anyway, thanks for everyone's efforts

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [December 1, 2015, 8:21am UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/8 "2015-12-01T08:21:25Z")

</div>

Thanks for letting us know 😉

---

<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:** [July 6, 2017, 1:46pm UTC](https://discuss.elastic.co/t/marvel-dashboard-wont-show-shards-infos/35525/9 "2017-07-06T13:46:35Z")

</div>


