In your logstash config file configure output similar to this:
output {
elasticsearch {
type => "eventlog"
index => "eventlog-%{+YYYY.MM.dd}"
cluster => "Scrat"
host => "localhost"
port => "9200"
* protocol => "http"*
idle_flush_time => 5
}
}
* protocol => "http" is what makes the difference*
On Friday, November 7, 2014 4:51:35 PM UTC-8, Glenn Howald wrote:
>
> Can you expand on "node" protocol and how I make logstash use http
> protocol?
>
> When I have the logstash agent turned off, kibana 4 page loads. When I
> turn on my logstash agent, kibana 4 says "This version of Kibana requires
> at least Elasticsearch 1.4.0.Beta1".
>
> On Friday, October 10, 2014 10:45:49 AM UTC-7, Konstantin Erman wrote:
>>
>> After all I've figured (with some help) that Kibana 4 uses node info API
>> to check that ALL nodes in the cluster are at least 1.4.0.Beta1, The trick
>> is that if you have Logstash talking to your ES, chances are it does so
>> using "node" protocol, effectively pretending to be extra nodes in cluster
>> which are obviously not of the right version. Switching Logstash to http
>> protocol does the trick of unblocking Kibana 4.0.0.Beta1.
>>
>> Konstantin
>>
>> On Wednesday, October 8, 2014 5:54:59 PM UTC-7, Konstantin Erman wrote:
>>>
>>> Today I have upgraded 3 machines development ES cluster from 1.3.2 to
>>> 4.0.0 BETA1. As far as I can tell it went successfully - cluster state is
>>> green, it responds to commands and all the data seems intact. New data keep
>>> coming in and indexing.
>>>
>>> BUT somehow I completely lost Kibana cooperation! I have Kibana 3.1.1
>>> running on port 80 in IIS and when I try access it as usual (
>>> http://tukc-devlog-1) I get back that new for 3.1.1 "Connection Failed"
>>> screen and whatever I do it does not connect!
>>>
>>> It says: "You will need to set http.cors.allow-origin in your
>>> elasticsearch.yml to the correct protocol, hostname, and port (if not 80)
>>> that your access Kibana from." ES, Kibana and browser are all on the same
>>> box, so I went to elasticsearch-1.4.0.Beta1\config\elasticsearch.yml and
>>> added this line:
>>>
>>> http.cors.allow-origin: "http://TUKC-DEVLOG-1";
>>>
>>> Restarted the node. Still same Connection Failed screen is all I get.
>>>
>>> Out of curiosity I tried Kibana 4.0.0 Beta1 too and the result was also
>>> negative, but even more confusing - "*This version of Kibana requires
>>> at least Elasticsearch 1.4.0.Beta1*" But that's exactly what I have
>>> running!
>>>
>>> I'm temporary out of ideas how to make either of them work.
>>>
>>> Any advice how to troubleshoot those two separate and probably different
>>> issues with Kibana?
>>>
>>> Thank you!
>>> Konstantin
>>>
>>
--
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/dacbd28c-4cdc-4f8a-b975-5001296dde74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
