Skip to content

Commit

Permalink
[8.8] [DOCS] Fixes errors in Troubleshoot Kibana UI error (elastic#15…
Browse files Browse the repository at this point in the history
…8855) (elastic#161139)

# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Fixes errors in Troubleshoot Kibana UI error
(elastic#158855)](elastic#158855)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kaarina
Tungseth","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-06-01T18:28:09Z","message":"[DOCS]
Fixes errors in Troubleshoot Kibana UI error (elastic#158855)\n\n##
Summary\r\n\r\nUpdates `Troubleshoot Kibana UI error` with the following
fixes:\r\n\r\n- {kib} in error code should Kibana\r\n- code shouldn’t
have “`” tick marks wrapping commands\r\n- the bullet list under Step#5
didn’t
format","sha":"c5f85b739369e4326d1518b4ab1458f39115fb74","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","backport:skip","v8.9.0","v8.10.0","v8.8.3"],"number":158855,"url":"https://github.com/elastic/kibana/pull/158855","mergeCommit":{"message":"[DOCS]
Fixes errors in Troubleshoot Kibana UI error (elastic#158855)\n\n##
Summary\r\n\r\nUpdates `Troubleshoot Kibana UI error` with the following
fixes:\r\n\r\n- {kib} in error code should Kibana\r\n- code shouldn’t
have “`” tick marks wrapping commands\r\n- the bullet list under Step#5
didn’t
format","sha":"c5f85b739369e4326d1518b4ab1458f39115fb74"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158855","number":158855,"mergeCommit":{"message":"[DOCS]
Fixes errors in Troubleshoot Kibana UI error (elastic#158855)\n\n##
Summary\r\n\r\nUpdates `Troubleshoot Kibana UI error` with the following
fixes:\r\n\r\n- {kib} in error code should Kibana\r\n- code shouldn’t
have “`” tick marks wrapping commands\r\n- the bullet list under Step#5
didn’t
format","sha":"c5f85b739369e4326d1518b4ab1458f39115fb74"}},{"branch":"8.10","label":"v8.10.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Kaarina Tungseth <[email protected]>
  • Loading branch information
jrodewig and KOTungseth authored Jul 4, 2023
1 parent 7766ce0 commit c1f10d8
Showing 1 changed file with 17 additions and 9 deletions.
26 changes: 17 additions & 9 deletions docs/setup/access.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -39,19 +39,27 @@ For JSON-formatted server status details, use the `localhost:5601/api/status` AP

[float]
[[not-ready]]
=== {kib} not ready
=== Troubleshoot {kib} UI error

If you receive an error that the {kib} `server is not ready`, check the following:
Troubleshoot the `Kibana Server is not Ready yet` error.

* The {es} connectivity:
. From within a {kib} node, confirm the connection to {es}:
+
[source,sh]
----
`curl -XGET elasticsearch_ip_or_hostname:9200/`
curl -XGET elasticsearch_ip_or_hostname:9200/
----
* The {kib} logs:
** Linux, DEB or RPM package: `/var/log/kibana/kibana.log`
** Linux, tar.gz package: `$KIBANA_HOME/log/kibana.log`
** Windows: `$KIBANA_HOME\log\kibana.log`
* The health status of `.kibana*` indices
. Guarantee the health of the three {kib}-backing indices. All indices must appear and display `status:green` and `status:open`:
+
[source,sh]
----
curl -XGET elasticsearch_ip_or_hostname:9200/_cat/indices/.kibana,.kibana_task_manager,.kibana_security_session?v=true
----
. <<start-stop,Shut down all {kib} nodes>>.
. Choose any {kib} node, then update the config to set the <<change-overall-log-level,debug logging>>.
. <<start-stop,Start the node>>, then check the start-up debug logs for `ERROR` messages or other start-up issues.
+
For example:

* When {kib} is unable to connect to a healthy {es} cluster, the `master_not_discovered_exception` or `Unable to revive connection` errors appear.
* When one or more {kib}-backing indices are unhealthy, the `index_not_green_timeout` error appears.

0 comments on commit c1f10d8

Please sign in to comment.