Failure with X-Pack Kibana-ES 5.6.4 X-Pack with Transport-Couchbase Cypress 3


#1

Failure with X-Pack Kibana-ES 5.6.4 X-Pack with Transport-Couchbase Cypress 3 on Centos 7.3+ everything works fine without the X-Pack. It is a non-dockered environment. When I install the X-Pack on ES ES works fine But after installing Kibana X-Pack, I get failure after it works fine for about 60 seconds. Following error when I try to re-create the same index that exists through ES. Please note, the index works fine for the first 60 seconds. Also, "Reporting" tab does not get included in "Discover". I am using the Basic edition license.

Error:

Fatal Error
Cannot read property 'toLowerCase' of undefined
Version: 5.6.4 Build: 15571
TypeError: Cannot read property 'toLowerCase' of undefined at http://ip-addr0:5601/bundles/kibana.bundle.js?v=15571:228:19006 at baseFindIndex (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:1:3037) at http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:1:31312 at http://ip-addr0:5601/bundles/kibana.bundle.js?v=15571:228:18946 at processQueue (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:38:23621) at http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:38:23888 at Scope.$eval (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:39:4619) at Scope.$digest (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:39:2359) at Scope.$apply (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:39:5037) at done (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:37:25027) at completeRequest (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:37:28702) at XMLHttpRequest.xhr.onload (http://ip-addr0:5601/bundles/commons.bundle.js?v=15571:37:29634)


#2

Hi Y'all!
Hope y'all are having a good holiday season. Following up on the above issue! Any thoughts on why x-pack is causing issues with the following configuration:

This is a non-docker install. Is there a Couchbase plugin for Kibana 6.1.1 and ES 6.1.1? I believe the latest Couchbase plugin is 5.6.4. Maybe upgrading to latest 6.1.1 will resolve this issue? But I'm sure more people have run into this issue with 5.6.4?

Thoughts, suggestions, recommendations?

Thanks!


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.