Installation of x-pack EPERM on Windows

[rowlandAtGitHub]

Kibana version: 5.0.0

Elasticsearch version:5.0.0

Server OS version:Windows 8.1

Browser version:IE 11

Browser OS version:Windows

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

Description of the problem including expected versus actual behavior:
Installation of kiban x-pack failed on Windows 8.1

Steps to reproduce:

1. Install elasticsearch 5.0.0
2. Install kibana 5.0.0
3. Install x-pack into elasticsearch 5.0.0
4. Install x-pack into kibana 5.0.0 fails

See forum discussion at https://discuss.elastic.co/t/installation-of-kibana-x-pack-failed-on-windows-8-1/65151
Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

[jbudz]

Still investigating but I'm guessing isaacs/node-graceful-fs#97 is the fix we want. I was able to install on a clean Windows 10 machine today, but @LeeDr was running into this yesterday.

[LeeDr]

On 5.1.0 release candidate;

D:\5.1.0\kibana>bin\kibana-plugin.bat install http://staging.elastic.co/5.1.0-1c632e3b/downloads/kibana-plugins/x-pack/x-pack-5.1.0.zip
Found previous install attempt. Deleting...
Attempting to transfer from http://staging.elastic.co/5.1.0-1c632e3b/downloads/kibana-plugins/x-pack/x-pack-5.1.0.zip
Transferring 107807209 bytes....................
Transfer complete
Retrieving metadata from plugin archive
Extracting plugin archive
Extraction complete
Plugin installation was unsuccessful due to error "EPERM: operation not permitted, rename 'D:\5.1.0\kibana\plugins\.plugin.installing' -> 'D:\5.1.0\kibana\plugins\x-pack'"
Unhandled rejection Error: EPERM: operation not permitted, rename 'D:\5.1.0\kibana\plugins\.plugin.installing' -> 'D:\5.1.0\kibana\plugins\x-pack'
    at Error (native)
    at fs.renameSync (fs.js:809:18)
    at D:\5.1.0\kibana\src\cli_plugin\install\install.js:51:24
    at undefined.next (native)
    at step (D:\5.1.0\kibana\src\cli_plugin\install\install.js:9:287)
    at tryCatcher (D:\5.1.0\kibana\node_modules\bluebird\js\main\util.js:26:23)
    at Promise._settlePromiseFromHandler (D:\5.1.0\kibana\node_modules\bluebird\js\main\promise.js:503:31)
    at Promise._settlePromiseAt (D:\5.1.0\kibana\node_modules\bluebird\js\main\promise.js:577:18)
    at Promise._settlePromises (D:\5.1.0\kibana\node_modules\bluebird\js\main\promise.js:693:14)
    at Async._drainQueue (D:\5.1.0\kibana\node_modules\bluebird\js\main\async.js:123:16)
    at Async._drainQueues (D:\5.1.0\kibana\node_modules\bluebird\js\main\async.js:133:10)
    at Immediate.Async.drainQueues (D:\5.1.0\kibana\node_modules\bluebird\js\main\async.js:15:14)
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5)

[ThaDafinser]

I tried instal 4 times now with 5.1.1

And the 4th was successfull - maybe increase the value for e.g. 2 seconds?

[jeremysintes]

Hi
I can see the error is closed but I still have it.
Did I miss something?

Kibana version: kibana-5.4.0-windows-x86

Elasticsearch version:5.4

Server OS version:Windows 7

Browser version:chrome 58.0.3029.110 (64-bit)

Browser OS version:Windows

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

Fails with: Plugin installation was unsuccessful due to error "EPERM: operation not permitte d, rename 'C:\tools\elastic\Kibana\plugins.plugin.installing' -> 'C:\tools\elastic\Kibana\plugins\x-pack'"

[jbudz]

The previous fix could be smarter, it waits and retries for up to three seconds. Reopening this, I'm thinking it could progressively try longer timeouts up to ~60 seconds .

[jeremysintes]

Thanks for your quick reply.
I solved my problem using the "installing x-pack on offline machine" approach.

[nreese]

Closing issue, x-pack is part of kibana since 6.3 and does not need to be installed any more