-
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
unsupported ES version should spit out a useful error #6048
Comments
I have to confirm, but I'm pretty sure newer versions of Kibana do provide a useful error message. |
Thanks... have not tested with 4.2 or 4.3 yet. |
Thank you @epixa. Just FWIW, kibana-4.1.4 (or anything >1) does not appear to be available in RPM format via the official 4.1 repo. |
That is correct - there was never any official coordinated effort to maintain the rpm distribution, it was just a single person going the extra mile. We're going to try to start coordinating it more officially starting in 4.4.0. |
Given that the ES version is trivial to get, Kibana should spit out a useful error message (i.e., "You're running an unsupported version of Elasticsearch; please consult https://www.elastic.co/support/matrix#show_compatibility") rather than "Error: Unknown error".
For example, Kibana 4.1.1 talking to ES 2.1.1 gives:
{"name":"Kibana","hostname":"xxx","pid":18465,"level":50,"err":{"message":"unknown error","name":"Error","stack":"Error: unknown error\n at respond (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:237:15)\n at checkRespForFailure (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n at HttpConnector.<anonymous> (/opt/kibana/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n at IncomingMessage.bound (/opt/kibana/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n at IncomingMessage.emit (events.js:117:20)\n at _stream_readable.js:944:16\n at process._tickCallback (node.js:442:13)"},"msg":"","time":"2016-01-29T18:53:45.740Z","v":0}
(or slightly different error if the .kibana index exists).
The text was updated successfully, but these errors were encountered: