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

Kibana4RC1 ElasticSearch Issue #3070

Closed
MiteshShah opened this issue Feb 18, 2015 · 3 comments
Closed

Kibana4RC1 ElasticSearch Issue #3070

MiteshShah opened this issue Feb 18, 2015 · 3 comments

Comments

@MiteshShah
Copy link

Hello All,

We have standalone ELK setup and just installed Kibana4 rc1 to test and get following errors:

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


Elasticsearch 1.1.1 @ inet[/10.10.10.10:9300] (192.168.0.1)
Error: This version of Kibana requires Elasticsearch 1.4.0 or higher on all nodes. I found the following incompatible nodes in your cluster: 


Elasticsearch 1.1.1 @ inet[/10.40.165.135:9300] (192.168.0.1)
    at SetupError (http://192.168.0.1:5601/index.js?_b=4673:43236:18)
    at http://192.168.0.1:5601/index.js?_b=4673:43430:17
    at wrappedCallback (http://192.168.0.1:5601/index.js?_b=4673:20764:81)
    at http://192.168.0.1:5601/index.js?_b=4673:20850:26
    at Scope.$eval (http://192.168.0.1:5601/index.js?_b=4673:21893:28)
    at Scope.$digest (http://192.168.0.1:5601/index.js?_b=4673:21705:31)
    at Scope.$apply (http://192.168.0.1:5601/index.js?_b=4673:21997:24)
    at done (http://192.168.0.1:5601/index.js?_b=4673:17570:45)
    at completeRequest (http://192.168.0.1:5601/index.js?_b=4673:17784:7)
    at XMLHttpRequest.xhr.onreadystatechange (http://192.168.0.1:5601/index.js?_b=4673:17723:11)```

Elasticsearch 1.1.1 @ inet[/10.40.165.135:9300] (50.23.202.85)
    at SetupError (http://50.23.202.85:5601/index.js?_b=4673:43236:18)
    at http://50.23.202.85:5601/index.js?_b=4673:43430:17
    at wrappedCallback (http://50.23.202.85:5601/index.js?_b=4673:20764:81)
    at http://50.23.202.85:5601/index.js?_b=4673:20850:26
    at Scope.$eval (http://50.23.202.85:5601/index.js?_b=4673:21893:28)
    at Scope.$digest (http://50.23.202.85:5601/index.js?_b=4673:21705:31)
    at Scope.$apply (http://50.23.202.85:5601/index.js?_b=4673:21997:24)
    at done (http://50.23.202.85:5601/index.js?_b=4673:17570:45)
    at completeRequest (http://50.23.202.85:5601/index.js?_b=4673:17784:7)
    at XMLHttpRequest.xhr.onreadystatechange (http://50.23.202.85:5601/index.js?_b=4673:17723:11)

As per image its seems like we have old ES 1.1.1 is running on port 9300.

But when i checked open ports and process id its logstash running on that port.

[root@elk]#  netstat -tulpn | grep 9300
tcp        0      0 :::9300                     :::*                        LISTEN      6169/java           
[root@elk]# ps ax | grep 6169
 6169 ?        SNl   31:59 /sbin/java -Djava.io.tmpdir=/var/lib/logstash -Xmx500m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -jar /opt/logstash/vendor/jar/jruby-complete-1.7.11.jar -I/opt/logstash/lib /opt/logstash/lib/logstash/runner.rb agent -f /etc/logstash/conf.d -l /var/log/logstash/logstash.log

Also we have ElasticSearch running on port 9200

{
  "status" : 200,
  "name" : "Veritas",
  "cluster_name" : "elasticsearch",
  "version" : {
    "number" : "1.4.3",
    "build_hash" : "36a29a7144cfde87a960ba039091d40856fcb9af",
    "build_timestamp" : "2015-02-11T14:23:15Z",
    "build_snapshot" : false,
    "lucene_version" : "4.10.3"
  },
  "tagline" : "You Know, for Search"
}
@barakSpoj
Copy link

I had the same issue and for a temporary quick workaround you can edit the 'check_es_version.js' file not to check the version:

replace:
if (versionmath.is('>=' + minimumElasticsearchVersion, versions)) {
for:
if(true){

@sdht0
Copy link

sdht0 commented Feb 18, 2015

Another workaround is to use 'elasticsearch_http' instead of 'elasticsearch' in logstash. Though I wonder why kibana searches for elasticsearch even when its url is given in the config.

@rashidkpc
Copy link
Contributor

Duplicate of #3049

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

4 participants