Fatal error when Kibana (4.1.0) with ES (1.6.0) on X86_64

Elastic Stack Kibana
1

Hi

I started Elasticsseach (1.6.0) and Kibana (4.1.0) on RHEL 6 (x86_64), but form browser got
following error msg:

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

Elasticsearch v1.0.3 @ inet[/xx.xx.xx.xx:9200] (9.26.54.179)
SetupError@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:46037:51
checkEsVersion/<@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:46266:1
qFactory/defer/deferred.promise.then/wrappedCallback@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:20893:15
qFactory/ref/<.then/<@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:20979:11
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:22022:9
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:21834:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:22126:13
done@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:17661:34
completeRequest@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:17875:7
createHttpBackend/</xhr.onreadystatechange@http://zrhelvm16.canlab.xxx.com:5601/index.js?_b=7467:17818:1

Why it detects ES is "v1.0.3", but in fact is 1.6.0.
BTW, if running ES (1.6.0) on win7, it works fine.

Thanks,

2

Is ES running on that IP? It could also be Logstash.

3

ES (1.6.0) indeed runs on that IP. No any Logstash is running.
What does "cluster" here means?

The config of kibana is like:

The Elasticsearch instance to use for all your queries.

elasticsearch_url: "http://localhost:9200"

Thanks

4

Did you leave Zen discovery and default cluster name "elasticsearch" in place? If so, it is also possible that some other test node with an older version connected to your elasticsearch cluster. Try changing the default cluster name and try again?

5

Thank Tanya,

After changing cluster name (not use default "elasticsearch" ) on ES side, it works for ES and Kibana.
We found there is a instance of ES running that uses the default cluster name and that causes the problems.

Thanks