Skip to content
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

Closed
gcobr opened this issue Feb 16, 2015 · 8 comments

Comments

@gcobr
Copy link

gcobr commented Feb 16, 2015

I am running Elasticsearch 1.4.3; however, the first time I started Kibana, the application showed me the following error message:

Kibana: This version of Kibana requires Elasticsearch 1.4.3 or higher on all nodes. I found the following incompatible nodes in your cluster: 

Elasticsearch 1.1.1 @ inet[/10.28.3.201:9301] ()

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.

@markwalkom
Copy link
Contributor

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.

@rogersmarin
Copy link

@markwalkom where/how can I configure that?

@markwalkom
Copy link
Contributor

@runesl
Copy link

runesl commented Feb 19, 2015

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.

@wrigby
Copy link

wrigby commented Feb 19, 2015

@rogersmarin Use the elasticsearch_http output plugin instead of the elasticsearch one for a quick workaround. I think this will be fixed in 4.0.0 - see #3066 .

@markwalkom
Copy link
Contributor

Don't use the elasticsearch_http output, it's being deprecated, use the elastisearch one with protocol => http

@wrigby
Copy link

wrigby commented Feb 19, 2015

@markwalkom woops... I didn't notice that. Thanks for the heads up!

@mingderwang
Copy link

To check and find some nodes in your elasticsearch cluster are running 1.1.1 es.
$ curl -XGET 'http://localhost:9200/_nodes?pretty=true'
Shutdown them with their node ID, such as
$ curl -XPOST 'http://localhost:9200/_cluster/nodes/i5Nk8Jp8RCaCUGWc_egSZQ/_shutdown'

It causes by logstash default come with its own embedded elasticsearch, which is 1.1.1 and will join the clustering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants