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

"yarn es snapshot" fails on Windows #20063

Closed
blfrantz opened this issue Jun 20, 2018 · 7 comments
Closed

"yarn es snapshot" fails on Windows #20063

blfrantz opened this issue Jun 20, 2018 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team

Comments

@blfrantz
Copy link
Contributor

Kibana version: Latest master (92245ac)

Elasticsearch version: 7.0.0-alpha1 snapshot

OS version: Windows 10

Describe the bug:
After syncing the kibana source (first time in a few days), yarn es snapshot fails for me as follows:

> yarn es snapshot
yarn run v1.6.0
$ node scripts/es snapshot
 info  Installing from snapshot
   │ info  version: 7.0.0-alpha1
   │ info  install path: F:\CodingProjects\kibana\kibana\.es\7.0.0-alpha1
   │ info  license: basic
   │ info  downloading from https://snapshots.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-alpha1-SNAPSHOT.tar.gz
   │ info  etags match, using cache from 2018-06-19T23:38:11.474Z
   │ info  install directory already exists, removing
   │ info  extracting F:\CodingProjects\kibana\kibana\.es\cache\elasticsearch-7.0.0-alpha1-SNAPSHOT.tar.gz
   │ info  extracted to F:\CodingProjects\kibana\kibana\.es\7.0.0-alpha1
   │ info  setting bootstrap password to changeme
   │ERROR  Unhandled error
   │ERROR  Error: spawn ./bin/elasticsearch-keystore.bat ENOENT
   │           at notFoundError (F:\CodingProjects\kibana\kibana\packages\kbn-es\node_modules\cross-spawn\lib\enoent.js:6:26)
   │           at verifyENOENT (F:\CodingProjects\kibana\kibana\packages\kbn-es\node_modules\cross-spawn\lib\enoent.js:40:16)
   │           at ChildProcess.cp.emit (F:\CodingProjects\kibana\kibana\packages\kbn-es\node_modules\cross-spawn\lib\enoent.js:27:25)
   │           at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
error Command failed with exit code 1.

It appears there is no elasticsearch-keystore.bat file in the .tar.gz file, yet there is in the .zip version. But it appears nothing has changed in kbn-es in the time that this stopped working, so I'm not sure how this used to work. Am I missing something? I could've sworn I didn't do anything different a few days ago...

@tylersmalley tylersmalley added bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team labels Jun 20, 2018
@tylersmalley
Copy link
Contributor

This is my bad, caused from #19916. I will get a fix in shortly.

@sbelyankin
Copy link

sbelyankin commented Jun 20, 2018

Same behavior observed with Kibana 6.3.0 on node:8.11.0-alpine. I am able to execute: yarn kbn clean, yarn kbn bootstrap, and yarn start to get Kibana up and running, but when executing yarn es snapshot or yarn es archive /opt/elasticsearch-6.3.0.tar.gz (.tar.gz is copied to /opt/ prior to executing the command), both fail with the following error message regarding ./bin/elasticsearch-keystore. Are there any parameters that can be passed to the yarn es command to fix this?

$ node scripts/es snapshot
 info  Installing from snapshot
   │ info  version: 6.3.0
   │ info  install path: /kibana/.es/6.3.0
   │ info  license: basic
   │ info  downloading from https://snapshots.elastic.co/downloads/elasticsearch/elasticsearch-6.3.0-SNAPSHOT.tar.gz
   │ info  extracting /kibana/.es/cache/elasticsearch-6.3.0-SNAPSHOT.tar.gz
   │ info  extracted to /kibana/.es/6.3.0
   │ info  setting bootstrap password to changeme
   │ERROR  Unhandled error
   │ERROR  Error: spawn ./bin/elasticsearch-keystore ENOENT
   │           at _errnoException (util.js:1022:11)
   │           at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
   │           at onErrorNT (internal/child_process.js:372:16)
   │           at _combinedTickCallback (internal/process/next_tick.js:138:11)
   │           at process._tickCallback (internal/process/next_tick.js:180:9)

@blfrantz
Copy link
Contributor Author

@sbelyankin I've found that simply starting the elasticsearch from the manually-downloaded snapshot works fine. For me (on Windows), this meant unzipping https://snapshots.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-alpha1-SNAPSHOT.zip and just running bin/elasticsearch.bat.

@acostache
Copy link

Hi @tylersmalley are there any updates on this? Is there a fix planned (or already available)?
Thank you!

@tylersmalley
Copy link
Contributor

This was caused by elastic/elasticsearch#30596 - I am working to update to pull the zip when on Windows.

@tylersmalley
Copy link
Contributor

I have opened a PR here: #20503

@tylersmalley
Copy link
Contributor

PR has been merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants