# TOO\_MANY\_REQUESTS/12/disk usage exceeded **URL:** \ **Category:** Kibana\ **Created:** [August 9, 2021, 1:49am UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753 "2021-08-09T01:49:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mfisher](https://avatars.discourse-cdn.com/v4/letter/m/ed655f/32.png) [@mfisher](https://discuss.elastic.co/u/mfisher)\ **Post date:** [August 9, 2021, 1:49am UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753/1 "2021-08-09T01:49:31Z")
Recently credentials are failing in the Kibana web interface. Checking the logs there is an error indicating disk usage is exceeded. {"type":"log","@timestamp":"2021-08-08T20:41:52-05:00","tags":["error","plugins","apm"],"pid":2366,"message":"Could not create index: '.apm-custom-link'. Error: cluster\_block\_exception: [cluster\_block\_exception] Reason: index [.apm-custom-link] blocked by: [TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];."} I've seen different references around on the net stating to "free up space" and then run these commands to unlock the indices. curl -XPUT -H "Content-Type: application/json" [http://10.6.67.30:9200/\_cluster/settings](http://10.6.67.30:9200/_cluster/settings) -d '{ "transient": { "cluster.routing.allocation.disk.threshold\_enabled": false } }' curl -XPUT -H "Content-Type: application/json" [http://10.6.67.30:9200/\_all/\_settings](http://10.6.67.30:9200/_all/_settings) -d '{"index.blocks.read\_only\_allow\_delete": null}' How do I go about safely deleting indices via the CLI since I cannot use the Kibana interface? Thanks, ---
**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:** [August 9, 2021, 4:48am UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753/2 "2021-08-09T04:48:22Z")
Check out [Delete index API | Elasticsearch Guide [7.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-index.html) ---
**Author:** ![Justin\_Gatewood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justin_gatewood/32/93515_2.png) [@Justin\_Gatewood](https://discuss.elastic.co/u/Justin_Gatewood)\ **Post date:** [August 20, 2021, 3:11pm UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753/3 "2021-08-20T15:11:32Z")
The question asked for how to safely delete indices when you are unable to access the Kibana interface. Your answer points to a process that requires access to the Kibana interface to work. What CMD/CLI options (if any) are available for deleting indices when Kibana won't start due to 'disk usage exceeded' notifications? I am having the same issue this morning - Kibana won't start - I am seeing the same in my terminal - I am using ELK on Windows, so CMD prompt options would also be helpful. ---
**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:** [August 23, 2021, 1:29am UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753/4 "2021-08-23T01:29:42Z")
In that doc link you can see the `Copy as curl` and that will let you run something directly from a shell, without the need for Kibana. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 20, 2021, 1:30am UTC](https://discuss.elastic.co/t/too-many-requests-12-disk-usage-exceeded/280753/5 "2021-09-20T01:30:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.