I have tried this, and kibana can connect to ES, but the state of ES turns 
to
orange, and in the config of kibana it defects on a timeout.

I have tried it with ES version 1.4.1 ub the kibana.jar, but that gives me 
the old error.



On Friday, January 2, 2015 10:42:07 PM UTC+1, Alexander Reynolds wrote:
>
> You can cheat Kibana's version check to get around this issue. Edit the 
> index.js file with the kibana.jar file (kibana/public) and change 
> 'minimumElasticsearchVersion' from '1.4.0' to '1.3.4'. I haven't done much 
> testing with this yet, but it does allow you to search through your indices 
> at least.
>
> Cheers,
> Al
>
> On Monday, December 8, 2014 10:17:20 AM UTC-5, Arie wrote:
>>
>> Hi Group,
>>
>> I am trying to look at the ES data with Kibana 4.0, but there is an
>> incompatibility with graylog2.
>>
>> It appears that Kibana joins ES as a node and conflicts with graylog-2.
>> When I shutdown graylog2-server it is possible to connect to ES with
>> kibana 4.
>>
>> Anyone an idea to work around this situation?
>>
>> tia.
>> Arie
>>
>
> Notice of Confidentiality: ***This E-mail and any of its attachments may 
> contain Lincoln National Corporation proprietary information, which is 
> privileged, confidential, or subject to copyright belonging to the Lincoln 
> National Corporation family of companies. This E-mail is intended solely 
> for the use of the individual or entity to which it is addressed. If you 
> are not the intended recipient of this E-mail, you are hereby notified that 
> any dissemination, distribution, copying, or action taken in relation to 
> the contents of and attachments to this E-mail is strictly prohibited and 
> may be unlawful. If you have received this E-mail in error, please notify 
> the sender immediately and permanently delete the original and any copy of 
> this E-mail and any printout. Thank You. ***

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to