-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Problem: This version of Kibana requires Elasticsearch 1.4.3 or higher on all nodes #3049
Comments
That'd be because you are using the node transport protocol, so LS joins the cluster as a node. Use the HTTP or transport protocols and you won't have this problem. |
@markwalkom where/how can I configure that? |
In your LS config, see http://logstash.net/docs/1.4.2/outputs/elasticsearch#protocol |
Kibana shoudn't detect logstash as an ES node, which it can draw data from. It's counterintuitive and makes elk unnecesarily difficult to setup. |
@rogersmarin Use the |
Don't use the |
@markwalkom woops... I didn't notice that. Thanks for the heads up! |
To check and find some nodes in your elasticsearch cluster are running 1.1.1 es. It causes by logstash default come with its own embedded elasticsearch, which is 1.1.1 and will join the clustering. |
I am running Elasticsearch 1.4.3; however, the first time I started Kibana, the application showed me the following error message:
After a brief investigation, I found out that the application listening on port 9301 was actually Logstash. It had nothing to do with Elasticsearch.
For some unexplained reason, Kibana thought it were an Elasticsearch server.
The text was updated successfully, but these errors were encountered: