# Graylog not indexing **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [January 11, 2019, 4:59am UTC](https://community.graylog.org/t/graylog-not-indexing/8336 "2019-01-11T04:59:42Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@grant](https://community.graylog.org/u/grant)\ **Post date:** [January 11, 2019, 4:59am UTC](https://community.graylog.org/t/graylog-not-indexing/8336/1 "2019-01-11T04:59:42Z")
Hi, The server ran out of space over night but gave it more space but now graylog wont index how do I clear the below? **There were 198,468 failed indexing attempts in the last 24 hours.** ``` srv_std_syslog__42 a2da2d21-155d-11e9-a927-0242ac120002 {"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"} ``` Thanks ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [January 11, 2019, 7:47am UTC](https://community.graylog.org/t/graylog-not-indexing/8336/2 "2019-01-11T07:47:58Z")
fix elasticsearch that it accept messages again ---
**Author:** ![grant](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@grant](https://community.graylog.org/u/grant)\ **Post date:** [January 11, 2019, 8:38am UTC](https://community.graylog.org/t/graylog-not-indexing/8336/3 "2019-01-11T08:38:23Z")
You would not have that handy for a elastic noob:) am using docker. ---
**Author:** ![macko003](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/macko003/32/3175_2.png) [@macko003](https://community.graylog.org/u/macko003)\ **Post date:** [January 11, 2019, 11:22am UTC](https://community.graylog.org/t/graylog-not-indexing/8336/4 "2019-01-11T11:22:03Z")
for noobs? say hello for your data, and start a new empty server. for users? say hello for your data. restart elastic with empty database. for pros? start a new empty server, wait for replication or restore the database 🙂 If you ran out of space the elastic database will have problem. The elasticsearch designed for distributed data sorage, so if you have a cluster a node loos won’t be a problem. But if you store all data on one node… Maybe you can do some research about how can you fix, but I administrate only HA systems, so I didn’t do it. I just drop out the wrong server, and wait for recover. ---
**Author:** ![Totally\_Not\_A\_Robot](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/totally_not_a_robot/32/3353_2.png) [@Totally\_Not\_A\_Robot](https://community.graylog.org/u/Totally_Not_A_Robot)\ **Post date:** [January 11, 2019, 1:22pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/5 "2019-01-11T13:22:34Z")
> [@macko003](#): > > for pros? start a new empty server, wait for replication or restore the database 🙂 Wait, are you saying Elastic simply cannot be saved after it has run out of disk space? Not even once? that would be very odd… Then again, you absolutely know a lot more about ES than I do 🙂 ---
**Author:** ![macko003](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/macko003/32/3175_2.png) [@macko003](https://community.graylog.org/u/macko003)\ **Post date:** [January 11, 2019, 1:40pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/6 "2019-01-11T13:40:15Z")
Onece I ran out of disk. After a restart elastic report a broken database, so I drop the elastic directory and wait for the replication, that was a test System. Now I monitor my systems better. ---
**Author:** ![macko003](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/macko003/32/3175_2.png) [@macko003](https://community.graylog.org/u/macko003)\ **Post date:** [January 11, 2019, 2:00pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/8 "2019-01-11T14:00:16Z")
Ok here is a solution. But it’s also mention data loose. [http://www.flax.co.uk/blog/2016/04/21/running-disk-space-elasticsearch-solr/](http://www.flax.co.uk/blog/2016/04/21/running-disk-space-elasticsearch-solr/) 1. jan. 11., P 14:32 dátummal Tess via Graylog Community [graylog@discoursemail.com](mailto:graylog@discoursemail.com) ezt írta: ---
**Author:** ![jtkarvo](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@jtkarvo](https://community.graylog.org/u/jtkarvo)\ **Post date:** [January 11, 2019, 6:01pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/9 "2019-01-11T18:01:55Z")
hi, you can just use CURL commands for the ES to check which indices are broken, and delete those. If that works out, you can get away with only partial data loss. ---
**Author:** ![Totally\_Not\_A\_Robot](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/totally_not_a_robot/32/3353_2.png) [@Totally\_Not\_A\_Robot](https://community.graylog.org/u/Totally_Not_A_Robot)\ **Post date:** [January 11, 2019, 6:22pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/10 "2019-01-11T18:22:02Z")
> [@jtkarvo](#): > > you can just use CURL commands for the ES to check which indices are broken, and delete those. If that works out, you can get away with only partial data loss. Yikes, that’s a pretty scary prospect though. One would hope there are ways of restoring broken indices. Some people rely upon the data in ElasticSearch for auditing etc. ---
**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:** [January 25, 2019, 6:30pm UTC](https://community.graylog.org/t/graylog-not-indexing/8336/11 "2019-01-25T18:30:32Z")
Closed on January 25, 2019, 6:30pm UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.