I had the same problem when I accidentially joined in cluster with a collegue who was using an older version of elasticsearch. Changed the cluster name and everything worked perfectly ;-)
/Stefan Den torsdag den 4. december 2014 08.01.09 UTC+1 skrev David Montgomery: > > > I added the below to elasticsearch.ymk config. Still kibana provides the > same error > > http.cors.enabled: true > http.cors.allow-origin: http://monitor-development-east.test.com:5601 > > For those at elastiseaerch..can you provide me color on what my be going > on? > > Thanks > > > > > > > > On Thursday, December 4, 2014 7:53:50 AM UTC+8, David Montgomery wrote: >> >> Hi, >> >> have no agents as of yet. Just logstash server with the below config >> >> input { >> redis { >> host => "<%=@redis_host%>" >> data_type => "list" >> key => "logstash" >> codec => json >> } >> } >> >> output { >> stdout { } >> elasticsearch { >> host => "<%=node[:ipaddress]%>" >> } >> } >> >> On Thursday, December 4, 2014 6:19:36 AM UTC+8, Jack Judge wrote: >>> >>> This tripped me up too. >>> >>> Are your logstash agents using the elasticsearch output ? If so, they'll >>> be running the embedded version of ES that comes with Logstash, and that's >>> the version that's stopping kibana from working. Basically *any* ES node >>> that connects to your cluster in any form must be 1.4.x >>> My solution was to change the logstash output to elasticsearch_http >>> >>> JJ >>> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5dad34dc-fe0f-4ab4-86bb-a33571fc434c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
