Installing X-pack breaks Kibana

[Diggy]

Hello, all.

I've just set up the ELK 5.4 stack on Ubuntu 16.04 LTS. I works fine. However, when I try to install X-pack for Elasticsearch and for Kibana, then refresh Kibana, I get this in my browser:

Error: Error: [$injector:unpr] Unknown provider: sessionTimeoutProvider <- sessionTimeout <- $http <- config
http://errors.angularjs.org/1.4.7/$injector/unpr?p0=sessionTimeoutProvider%20<-%20sessionTimeout%20<-%20%24http%20<-%20config (https://elk01.netatlantic.com.backend/bundles/commons.bundle.js?v=15104:35)
[2491]/window.onerror@https://elk01.netatlantic.com.backend/bundles/commons.bundle.js?v=15104:91:17941

I then restart the stack, and get this in my browser:

Firefox has detected that the server is redirecting the request for this address in a way that will never complete (particular browser makes no difference).

If I then uninstall X-pack for Kibana, I get this:

ui settings Elasticsearch plugin is red
plugin:kibana@5.4.1 Ready
plugin:elasticsearch@5.4.1 Authentication Exception

If I then uninstall X-pack for Elasticsearch, I'm all good again. What's going on? Do I need to install X-pack for Elasticsearch, Logstash, and Kibana? What's the purpose of X-pack for each? And, finally, the most important question - How do I successfully install X-pack in my system?

Many thanks.

[Bargs (Matt Bargar)]

This sounds like there may have been an issue with transpiling the kibana source code when installing x-pack in kibana. Could you try the recommended steps in this comment?

To answer your other question, the x-pack plugin for each system provides functionality specific to that system. Take monitoring for example. X-pack for elasticsearch adds a collector for monitoring data. X-pack for logstash adds functionality that sends more monitoring data to elasticsearch. X-pack for kibana adds a monitoring UI which consumes the data provided by x-pack for elasticsearch and logstash. It's a similar story for each piece of x-pack.

[Diggy]

Thanks, Bargs. I'll follow the steps recommended in the comment. That seems to relate to Kibana. Must I do something similar for Elasticsearch and Logstash X-pack?

[Diggy]

Alas, no joy. I followed the steps in the comment, although I never found a file named "babel-cache.json" anywhere. I rebooted the machine, and note that, while kibana reports as started, no port 5601 has been opened. What else should I try?

[Diggy]

Bargs, I take it all back. It did work. I had to install the elasticsearch x-pack, then reboot, then wait several minutes. Looks like Kibana with X-pack is all good now. Thanks so much!!