# Graylog dashboard is looking good due to below error

**URL:** <https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892>\
**Category:** Graylog Central (peer support)\
**Created:** [May 19, 2021, 4:40am UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892 "2021-05-19T04:40:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![deepakkumardubey](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/deepakkumardubey/32/8664_2.png) [@deepakkumardubey](https://community.graylog.org/u/deepakkumardubey)\
**Post date:** [May 19, 2021, 4:40am UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/1 "2021-05-19T04:40:12Z")

</div>

Hello Friends,

I have set up my Graylog on the docker container while getting the below error.

Errors:

Error response from daemon: configured logging driver does not support reading.  
rerouting shards: [high disk watermark exceeded on one or more nodes]  
high disk watermark [90%] exceeded on high disk watermark exceeded on one or more nodes

---

<div class="post-metadata">

**Author:** ![reimlima](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/reimlima/32/16254_2.png) [@reimlima](https://community.graylog.org/u/reimlima)\
**Post date:** [May 19, 2021, 10:34am UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/2 "2021-05-19T10:34:58Z")

</div>

Hi,

this error means that one node in you elasticsearch cluster is facing disk utilization issues.

It’s a good thing apply a index rotation policy in your ES cluster to migrate and purge old data.

---

<div class="post-metadata">

**Author:** ![deepakkumardubey](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/deepakkumardubey/32/8664_2.png) [@deepakkumardubey](https://community.graylog.org/u/deepakkumardubey)\
**Post date:** [May 20, 2021, 9:50am UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/3 "2021-05-20T09:50:02Z")

</div>

Hi Renaldo,

Disk space resolved but still same error.  
Regards,  
Deepak

---

<div class="post-metadata">

**Author:** ![reimlima](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/reimlima/32/16254_2.png) [@reimlima](https://community.graylog.org/u/reimlima)\
**Post date:** [May 20, 2021, 1:23pm UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/4 "2021-05-20T13:23:55Z")

</div>

Hi,

Two likely mistakes here:

1. you did not free enough space (or the disk is full again)
2. you freed space in the wrong node

---

<div class="post-metadata">

**Author:** ![jstale](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jstale/32/8631_2.png) [@jstale](https://community.graylog.org/u/jstale)\
**Post date:** [May 20, 2021, 7:12pm UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/5 "2021-05-20T19:12:28Z")

</div>

I have run this command after freeing up diskspace to get things rolling again:

```auto
curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [June 3, 2021, 7:13pm UTC](https://community.graylog.org/t/graylog-dashboard-is-looking-good-due-to-below-error/19892/6 "2021-06-03T19:13:23Z")

</div>

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