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

Wrong error: "Upgrade Required Your version of Elasticsearch is too old. Kibana requires Elasticsearch 0.90.9 or above." #2056

Closed
lathspell opened this issue Nov 11, 2014 · 16 comments

Comments

@lathspell
Copy link

After installing logstash=1.4.2-1-2c0f5a1 I started logstash-web but did not notice that logstash itself was not running. When pointing my browser to the web interface, it just gave me the error:

Upgrade Required Your version of Elasticsearch is too old. Kibana requires Elasticsearch 0.90.9 or above.

This is wrong, I installed the Logstash Debian package which bundles Elasticsearch 1.1.1. As a newbie was puzzled and removed / downloaded / reinstalled the package several times until I noticed that there was a second error message:

Error Could not reach http://localhost:9200/_nodes. If you are using a proxy, ensure it is configured correctly

Maybe this could be improved so that it says "... If you use the bundled Elasticsearch, make sure the logstash agent daemon is running, if you use a dedicated Elasticsearch daemon, check if is in version 0.90.9 or higher!"

@jsvd
Copy link
Member

jsvd commented Nov 11, 2014

This comes from Kibana 3.0.1, that ships with Logstash 1.4.2.

Logstash 1.5 will ship with Kibana 3.1.0 or 3.1.2 that improve this error handling. 3.1.2 actually has some troubleshooting tips that target this particular issue too.

So this will be improved in the next version, thanks for reporting.

@jianfengye
Copy link

I got the same error when i use logstash-1.4.2 ,

@dweinstein
Copy link

So what's the way to fix/get rid of this error?

@electrical
Copy link
Contributor

When running Logstash with node protocol ( which is by default ) its part of the cluster.
Kibana sees that as an other node which has an to older version of ES.
if you run LS with the ES output set to protocol => transport it should solve the issue.

@jianfengye
Copy link

i use kibana 3.0.1 not the one which in logstash. the versions follow the download page:http://www.elasticsearch.org/overview/elkdownloads/

@kervinpierre
Copy link

This is a misleading error. The problem is often with ElasticSearch CORS settings. See...
http://stackoverflow.com/a/26884367/16549

Pretty much add...

http.cors.allow-origin: "/.*/"
http.cors.enabled: true

To your elasticsearch.yml then restart.

@MarkMurphy
Copy link

http.cors.allow-origin: "/.*/"
http.cors.enabled: true

This worked for me. Added it to my elasticsearch.yml

@cfeller
Copy link

cfeller commented Feb 3, 2015

This is a misleading error. The problem is often with ElasticSearch CORS settings. See...
http://stackoverflow.com/a/26884367/16549

Misleading indeed - thank you Kervin.

@FatmaG
Copy link

FatmaG commented Feb 5, 2015

Greatly misleading!! Thank you!

@smancke
Copy link

smancke commented Feb 18, 2015

http.cors.allow-origin: "/.*/"
http.cors.enabled: true

Great, also solved it for me!!

@fb64
Copy link

fb64 commented Mar 11, 2015

Working also for me. Thanks :)

@Mindscope
Copy link

For me worked as follows:

http.cors.allow-origin: "*"
http.cors.enabled: true

@ckuharski-drc
Copy link

Worked for me. Thanks!

@spmkd
Copy link

spmkd commented Apr 18, 2015

Worked for me as well.

@enilu
Copy link

enilu commented May 6, 2015

http.cors.allow-origin: "/.*/"
http.cors.enabled: true

me too,thank you!!!

@jordansissel
Copy link
Contributor

For Logstash 1.5.0, we've moved all plugins to individual repositories, so I have moved this issue to logstash-plugins/logstash-output-elasticsearch#147. Let's continue the discussion there! :)

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