Kibana fails to start when Elasticsearch is not available #7234
Labels
bug
Fixes for quality problems that affect the customer experience
Comments
epixa
added
the
bug
|
@kimchy I created the issue so we can track it, but I am unable to reproduce the error you encountered on either an official build of |
|
#7106 related |
|
Ah, yeah, thanks. This is definitely a duplicate of #7106 |
cee-chen
added a commit
that referenced
this issue
Oct 4, 2023
`v88.5.0`⏩`v88.5.4` This EUI upgrade helps unblock the Shared UX team with some beta serverless nav updates not listed in the below changelog (elastic/eui#7228 and elastic/eui#7248). --- ## [`88.5.4`](https://github.com/elastic/eui/tree/v88.5.4) - This release contains internal changes to a beta component needed by Kibana. ## [`88.5.3`](https://github.com/elastic/eui/tree/v88.5.3) **Bug fixes** - Fixed `EuiComboBox` search input width not resetting correctly on selection ([#7240](elastic/eui#7240)) ## [`88.5.2`](https://github.com/elastic/eui/tree/v88.5.2) **Bug fixes** - Fixed broken `EuiTextTruncate` testenv mocks ([#7234](elastic/eui#7234)) ## [`88.5.1`](https://github.com/elastic/eui/tree/v88.5.1) - Improved the performance of `EuiComboBox` by removing the `react-autosizer-input` dependency ([#7215](elastic/eui#7215)) **Dependency updates** - Updated `react-element-to-jsx-string` to v5.0.0 ([#7214](elastic/eui#7214)) - Removed unused `@types/vfile-message` dependency ([#7214](elastic/eui#7214))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discovered by @kimchy
Kibana Version: 5.0.0-alpha2
What you did:
Tried to start kibana (ie.
bin/kibana) when Elasticsearch was not running.What happened:
A fatal error was encountered at startup and Kibana failed to start:
What should have happened:
Kibana should still have started, though it would log the following warning to console, and any user that accessed Kibana in the browser would be redirected to the status page where Elasticsearch would be marked as unavailable.
The text was updated successfully, but these errors were encountered: