Skip to content

Commit 1eb6f74

Browse files
authored
Update kibana/error-server-not-ready.md (#1937)
👋 Adds that Kibana requires `security` feature state to be working as well ([reference](https://medium.com/@stefnestor/diving-into-elasticsearch-security-f0a10ebd1d43)).
1 parent 31869ca commit 1eb6f74

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

troubleshoot/kibana/error-server-not-ready.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To troubleshoot the `Kibana server is not ready yet` error, try these steps:
2525
2. Guarantee the health of the three {{kib}}-backing indices. All indices must appear and display `status:green` and `status:open`:
2626

2727
```sh
28-
curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session?v=true
28+
curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session,.security*?v=true
2929
```
3030

3131
These {{kib}}-backing indices must also not have [index settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-settings) flagging `read_only_allow_delete` or `write` [index blocks](elasticsearch://reference/elasticsearch/index-settings/index-block.md).

0 commit comments

Comments
 (0)