Dev Build: Visualization Editor: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];:


(Eugene Fedotov) #1

I started using the dev build from GitHub. When I try to save a visualization, I get

"Visualization Editor: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"

I want to work on some issues that require a populated list of items.


(Felix Stürmer) #2

Hi @eugenefedoto,

does the kibana system user have write permissions on the .kibana index (or whatever the index name was configured to be)? Does that only happen for visualizations or also for dashboards and saved searches?


(Eugene Fedotov) #3

First, here's the entire stack trace from when I'm trying to save a visualization

Error: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
    at http://localhost:5601/twj/bundles/kibana.bundle.js?v=8467:57750:19
    at processQueue (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:47107:37)
    at http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:47151:27
    at Scope.$digest (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:48289:15)
    at Scope.$apply (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:48587:24)
    at done (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42608:47)
    at completeRequest (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42834:7)
    at XMLHttpRequest.requestLoaded (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42762:9)

I'm using Windows 10 Home.

does the kibana system user have write permissions on the .kibana index (or whatever the index name was configured to be)

I'm the admin of the system where Kibana is installed. The index name is logstash-0. I don't know where the index is stored on Windows.

Does that only happen for visualizations or also for dashboards and saved searches?

This is what I get from trying to save a dashboard.

Error: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
    at http://localhost:5601/twj/bundles/kibana.bundle.js?v=8467:57750:19
    at processQueue (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:47107:37)
    at http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:47151:27
    at Scope.$digest (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:48289:15)
    at Scope.$apply (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:48587:24)
    at done (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42608:47)
    at completeRequest (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42834:7)
    at XMLHttpRequest.requestLoaded (http://localhost:5601/twj/bundles/commons.bundle.js?v=8467:42762:9)

Not sure how to save a search, since I don't have anything to search for (also first time user, so I might not know how).


(Felix Stürmer) #4

This looks like your .kibana index is configured as read-only. You can see that by sending the following request using the Kibana devtools:

GET .kibana/_settings

Looking at the Elasticsearch log output might give an indication about the reason too.


(Kerem Can) #5

I changed the my kibana settings with

PUT .kibana/_settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false>"
}
}
}

but it resets itself after each process. any suggestion?


(Felix Stürmer) #6

Would it be possible for you to post the full index settings as returned by GET .kibana/_settings?


#7

I am experiencing the same issue. This is a fresh install with little to no custom changes.

my kibana setting output:

{
".kibana": {
"settings": {
"index": {
"number_of_shards": "1",
"blocks": {
"read_only_allow_delete": "true"
},
"provided_name": ".kibana",
"creation_date": "1511984561925",
"number_of_replicas": "1",
"uuid": "95cOtsa8S6y83KP_3MZ6IQ",
"version": {
"created": "6000099"
}
}
}
}
}


(Felix Stürmer) #9

I can not reproduce it using the following steps:

  • clone elasic/elasticsearch from github, check out master branch
  • run Elasticsearch via gradle run in the Elasticsearch directory
  • clone elastic/kibana from github, check out the master branch
  • run npm install in the Kibana directory
  • run npm start in the Kibana directory

Could you tell me what your git HEAD points to and whether you performed any diverging steps?


(Clood) #10

i can reproduce
i downloaded today last elastic6, kibana6 on windows
try to insert data

error inserting data
,{"update":{"_index":"ban","_type":"ban","_id":"ADRNIVX_0000000276223880","status":403,"error":{"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}}}]}

error on kibana

blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];


(Felix Stürmer) #11

If the read-only status is set repeatedly as you indicated before, my best guess is that Elasticsearch does not deem it safe to leave the indices in writable state. There are several conditions that can cause this, e.g. low free disk space. Could you please check the Elasticsearch log for any indication of why it set the indices to read-only?


(system) #12

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