Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not install x-pack plugin on Kibana-5.5.2 or 6.0.0.beta1 #13691

Closed
jklappenbach opened this issue Aug 24, 2017 · 3 comments
Closed

Can not install x-pack plugin on Kibana-5.5.2 or 6.0.0.beta1 #13691

jklappenbach opened this issue Aug 24, 2017 · 3 comments
Labels
feedback_needed Team:Operations Team label for Operations Team

Comments

@jklappenbach
Copy link

Kibana version: both kibana-5.5.2-darwin-x86_64 and kibana-6.0.0-beta1-darwin-x86_64, fresh installs

Elasticsearch version: elasticsearch-5.5.2 and elasticsearch-6.0.0-beta1, respectively

Server OS version: macOS Sierra, Version 10.12.6

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.): Download page

Description of the problem including expected versus actual behavior:

Expected successful install of plugin. Instead, I received the error message:

Plugin installation was unsuccessful due to error "regeneratorRuntime is not defined"

Steps to reproduce:

  1. Install x-pack plugin on elastic search:

elasticsearch/bin/elasticsearch-plugin install x-pack
...
This plugin launches a native controller that is not subject to the Java
security manager nor to system call filters.

Continue with installation? [y/N]y
-> Installed x-pack

  1. Install x-pack on kibana

kibana/bin/kibana-plugin install x-pack
Attempting to transfer from x-pack
Attempting to transfer from https://artifacts.elastic.co/downloads/kibana-plugins/x-pack/x-pack-6.0.0-beta1.zip
Transferring 118720680 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Optimizing and caching browser bundles...
Plugin installation was unsuccessful due to error "regeneratorRuntime is not defined"

I have been working with babel/es6/7, using them for standard react.js development. Perhaps there are libs via npm that are interfering. However, I've never run into versioning issues like this before.

@epixa
Copy link
Contributor

epixa commented Aug 24, 2017

We have a bug in Kibana at the moment that doesn't allow people to run the CLI command directly from inside the bin directory. Can you run bin/kibana-plugin install from the root of Kibana and see if that works?

@jklappenbach
Copy link
Author

Running from 'root', using ./bin/kibana-plugin install didn't help.

@snide snide added the Team:Operations Team label for Operations Team label Aug 7, 2018
@jbudz
Copy link
Member

jbudz commented Aug 15, 2018

I'm going to close this out, lets reopen if it comes up again. regeneratorRuntime is usually something with using async/await and not including babel-polyfill. We have the polyfill included now.

@jbudz jbudz closed this as completed Aug 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback_needed Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

5 participants