# Error starting Metricbeat

**URL:** <https://discuss.elastic.co/t/error-starting-metricbeat/142088>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [July 30, 2018, 4:29am UTC](https://discuss.elastic.co/t/error-starting-metricbeat/142088 "2018-07-30T04:29:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [July 30, 2018, 3:39pm UTC](https://discuss.elastic.co/t/error-starting-metricbeat/142088/2 "2018-07-30T15:39:07Z")

</div>

I can think of two causes for this.

Are you using any Security features? (Do you have a security section under Management, in Kibana?) Access restrictions can be forbidding metricbeat to access the .kibana index.

Another cause can be a problem as described in this post:

> [@FORBIDDEN/12/index read-only / allow delete (api)\]](https://discuss.elastic.co/t/forbidden-12-index-read-only-allow-delete-api/110282/2):
>
> I'm currently having the same issue with some ES indices. I'd say it has nothing to do with Logstash. For me, the issue started occurring after the file system of the server running Elasticsearch had been over its threshold. I tried restarting the cluster (currently a single node), but to no avail. The only thing that helped was reindexing the data in order not to lose anything, then deleting the existing indices. I'm still trying to solve the same issue for the .kibana index though. Any adv…

For which the solution is to run this command in Kibana -\> Dev Tools -\> Console:

> PUT .kibana/\_settings  
> {  
> "index": {  
> "blocks": {  
> "read\_only\_allow\_delete": "false"  
> }  
> }  
> }

---

_[View the full topic](https://discuss.elastic.co/t/error-starting-metricbeat/142088)._