# Issue with Logstash

**URL:** <https://discuss.elastic.co/t/issue-with-logstash/131343>\
**Category:** Logstash\
**Created:** [May 10, 2018, 6:53pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343 "2018-05-10T18:53:17Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandeepnarla22322](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sandeepnarla22322](https://discuss.elastic.co/u/sandeepnarla22322)\
**Post date:** [May 10, 2018, 6:53pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/1 "2018-05-10T18:53:18Z")

</div>

usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:385] elasticsearch - retrying failed action with response code: 403 ({"type"=\>"cluster\_block\_exception", "reason"=\>"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"})

I have 5000 files which need to be processed every five minutes, I do have 1.7 G available

logstash runs fine for 2 couples hours and it crashes with the above-mentioned error. I don't see any data in kibana and It's recurring not sure what is causing this error

below is the attached logstash.configuration

input {  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SES\_VG1/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sesvg1"  
}  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SES\_VG1\_Disk/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sesvg1disk"  
}  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SES\_VG2/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sesvg2"  
}  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SPP\_VG1/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sppvg1"  
}  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SPP\_VG1\_Disk/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sppvg1disk"  
}  
file {  
path =\>"/home/shared/msdp/LogStashOutputFormatted/SPP\_VG2/_.csv"  
start\_position =\> "beginning"  
sincedb\_path =\> "/dev/null"  
type =\> "sppvg2"  
}  
}

filter {  
if [type] == "sesvg1disk" or [type] == "sppvg1disk"{  
csv {  
separator =\> ","  
columns =\> ["nodeName","Filesystem","Size","Used","Avail","Utilization","MountedOn"]  
}  
}  
else if [type] == "sppvg1"{  
csv {  
separator =\> "/"  
columns =\> ["nodeName","APIName","Value","Share","Total"]  
}  
}  
else if [type] == "sppvg2"{  
csv {  
separator =\> ","  
columns =\> ["nodeName","APIName","Value","Share","Total"]  
}  
}  
else {  
csv {  
separator =\> ","  
columns =\> ["nodeName","APIName","Status","Share","Total"]  
}  
}  
mutate {  
convert =\> { "Filesystem" =\> "string" }  
convert =\> { "Size" =\> "string" }  
convert =\> { "Used" =\> "string" }  
convert =\> { "Avail" =\> "string" }  
convert =\> { "Utilization" =\> "integer" }  
convert =\> { "MountedOn" =\> "string" }  
convert =\> { "nodeName" =\> "string" }  
convert =\> { "APIName" =\> "string" }  
convert =\> { "Status" =\> "string" }  
convert =\> { "Value" =\> "string" }  
convert =\> { "Share" =\> "float" }  
convert =\> { "Total" =\> "integer" }  
}  
}

output {  
if [type] == "sesvg1" {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsesvg1"  
}  
}  
else if [type] == "sesvg1disk" {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsesvg1disk"  
}  
}  
else if [type] == "sppvg1" {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsppvg1"  
}  
}  
else if [type] == "sppvg1disk" {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsppvg1disk"  
}  
}  
else if [type] == "sppvg2" {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsppvg2"  
}  
}  
else {  
elasticsearch {  
action =\> "index"  
hosts =\> "[http://localhost:9200](http://localhost:9200)"  
index =\> "beatsesvg2"  
}

---

<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:** [May 10, 2018, 6:56pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/2 "2018-05-10T18:56:07Z")

</div>

This error typically mean that you are running out of disk space and have exceeded the 95% flooding [watermark](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html).

Moved it to the Logstash category.

---

<div class="post-metadata">

**Author:** ![sandeepnarla22322](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sandeepnarla22322](https://discuss.elastic.co/u/sandeepnarla22322)\
**Post date:** [May 10, 2018, 7:27pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/3 "2018-05-10T19:27:27Z")

</div>

Thanks for responding back

My disk utilization is at 92 percent and I did run the following command

curl -X PUT "localhost:9200/\*/\_settings" -H 'Content-Type: application/json' -d'{"index.blocks.read\_only\_allow\_delete": null}' , but it didn't help

you meant every time 95 percent it will stop working

is there a work around apart from increasing disk space

---

<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:** [May 10, 2018, 7:38pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/4 "2018-05-10T19:38:12Z")

</div>

Indexing can result in a lot of merging taking place, which will make the amount of used disk space go up and down. As running out of disk space can have serious consequences, I would recommend adding more by scaling up or out the cluster.

---

<div class="post-metadata">

**Author:** ![sandeepnarla22322](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sandeepnarla22322](https://discuss.elastic.co/u/sandeepnarla22322)\
**Post date:** [May 10, 2018, 7:43pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/5 "2018-05-10T19:43:38Z")

</div>

I have 30 G in a new partition changing the path.data and path.logs to different paths would help??

---

<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:** [May 11, 2018, 7:09am UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/6 "2018-05-11T07:09:03Z")

</div>

If you only have a single node adding this as an additional data path may not help as I believe Elasticsearch will not relocate shards between data paths on the same node.

---

<div class="post-metadata">

**Author:** ![sandeepnarla22322](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sandeepnarla22322](https://discuss.elastic.co/u/sandeepnarla22322)\
**Post date:** [May 11, 2018, 3:11pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/7 "2018-05-11T15:11:19Z")

</div>

Thanks

---

<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:** [June 8, 2018, 3:11pm UTC](https://discuss.elastic.co/t/issue-with-logstash/131343/8 "2018-06-08T15:11:31Z")

</div>

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