-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kibana crashes on startup if elasticsearch is started simultaneously #33689
Comments
Hi @redbaron4 |
I can confirm that on What you are seeing is a cluster state failure (master is not up or there is no replica of the |
@sebelga Thanks for looking at this. Does this mean that kibana crashing when there is a cluster state failure is expected behaviour? Would it be possible to mitigate this expected behaviour so that kibana service stays up and allows elasticsearch to recover in case such a thing ever happens in production? |
Sorry, I went a bit fast closing the issue and it might be an issue on our migration plugin. @marius-dr can you have a look into it? |
Pinging @elastic/kibana-operations |
I'm having the same issue with the docker image for Kibana 6.7.0 |
We are running into what seems to be the same issue with 6.8.1. In our case we upgraded from 6.5.4, with the intent on upgrading to 7.3.1, and while ES is running just fine, Kibana won't connect with the same errors as above. Checking the indexes in ES shows that there is a index called .kibana_1 and .monitoring-kibana-<today's date> with both a single primary and replica shard. Is there a suggested solution? Or temp mitigation? |
I've a similar problem with Kibana (version 6.8.2). Elastic needs a few minutes for starting up and changing its status from red to green. When Kibana is started at the same time as elastic it crashes with "all shards failed". I was wondering how this issue differs from the linked one #25027 that was supposed to be fixed by #25255. And #33316 describes a very similar problem. |
Might be fixed in 7.5.0 by https://github.com/elastic/kibana/pull/51324/files |
Closing as this should be resolved by #51324. Please let us know if you see this issue come up again. |
Kibana version: 6.6.0
Elasticsearch version: 6.6.0
Server OS version: CentOS-6.8
Browser version: firefox-52ESR
Browser OS version: Any
Original install method (e.g. download page, yum, from source, etc.): Install from RPM provided in download page
Describe the bug: Starting up Kibana and elasticsearch simultaneously causes kibana to exit with fatal error. This is almost identical to #25027 except that I faced this issue in 6.6.0.
I ran into this bug when our infrastructure was restarted after a power shutdown. Elasticsearch and Kibana are hosted on different machines. ES went into "red" (unallocated primary shards) on startup and took a while to complete recovery. Meanwhile, kibana started and crashed with the logs given below. My guess is that
.kibana
shards were unalloocated and the index was unusable.Steps to reproduce:
.kibana
shard)Expected behavior: Kibana should remain running even if it cannot access its own data on ES and show a similar prompt on browser.
Provide logs and/or server output (if relevant):
The logs for
stdout
The logs in
stderr
The text was updated successfully, but these errors were encountered: