Closed mikeforbes closed 4 years ago
Hi Mike, I'm in trouble with the same issue. Did you find any workaround or patch to solve this ? Environment: kibana 4.5.4 and trying to install html plugin. The process is running in packer. We're packaging a RHEL7 AMI.
Plugin install is randomly killed while doing 'Optimizing and caching browser bundles...' amazon-ebs: + ./bin/kibana plugin -i kibana-html-plugin -u https://github.com/raystorm-place/kibana-html-plugin/releases/download/v0.0.3/kibana-html-plugin-v0.0.3.tar.gz amazon-ebs: Installing kibana-html-plugin amazon-ebs: Attempting to transfer from https://github.com/raystorm-place/kibana-html-plugin/releases/download/v0.0.3/kibana-html-plugin-v0.0.3.tar.gz amazon-ebs: Transferring 2260613 bytes.................... amazon-ebs: Transfer complete amazon-ebs: Extracting plugin archive amazon-ebs: Extraction complete amazon-ebs: Optimizing and caching browser bundles... amazon-ebs: /tmp/script_4105.sh: line 130: 9454 Killed ./bin/kibana plugin -i kibana-html-plugin -u https://github.com/raystorm-place/kibana-html-plugin/releases/download/v0.0.3/kibana-html-plugin-v0.0.3.tar.gz ==> amazon-ebs: Terminating the source AWS instance...
As a workaround we're building the AMI with a larger EC2 instance so that we don't run into this strange Kibana timeout issue.
@regel Yeah, I just stopped using kibana plugins.
Be nice to get a fix though...
I'm also running into this issue on a virtual machine, guess there isn't enough RAM.
I wonder if the default timeout value of 0 might be being ignored somehow..
My ansible playbook task seems to think a successful plugin install fails (it probably takes so long as it's running on my laptop in a vm) e.g
It is installed successfully, but the "Killed" means it's causing my ansible task to call it a failure.
The real issue however, is the timeout values seem to be ignored:
I tried adding a timeout value and I get:
other values seem to have no effect:
running kibana 4.4.1, ubuntu package installed from the elastic debian repo