# \[SOLVED\] Filebeats not writing data

**URL:** <https://discuss.elastic.co/t/solved-filebeats-not-writing-data/128143>\
**Category:** Elasticsearch\
**Created:** [April 16, 2018, 9:05am UTC](https://discuss.elastic.co/t/solved-filebeats-not-writing-data/128143 "2018-04-16T09:05:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![astropanic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/astropanic/32/20726_2.png) [@astropanic](https://discuss.elastic.co/u/astropanic)\
**Post date:** [April 16, 2018, 9:05am UTC](https://discuss.elastic.co/t/solved-filebeats-not-writing-data/128143/1 "2018-04-16T09:05:06Z")

</div>

Hi, my Nginx Filebeat module stopped to write data to ES.

({"type"=\>"cluster\_block\_exception", "reason"=\>"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]

It was solved by:

PUT \_settings  
{  
"index": {  
"blocks": {  
"read\_only\_allow\_delete": "false"  
}  
}  
}

But why the index got in read-only state in the first place?  
How I can debug and prevent such situations?

---

<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:** [April 16, 2018, 9:10am UTC](https://discuss.elastic.co/t/solved-filebeats-not-writing-data/128143/2 "2018-04-16T09:10:04Z")

</div>

That is often a sign that you are running out of disk space in Elasticsearch and have exceeded the [flood-stage watermark](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html).

---

<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:** [May 14, 2018, 9:10am UTC](https://discuss.elastic.co/t/solved-filebeats-not-writing-data/128143/3 "2018-05-14T09:10:11Z")

</div>

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