Kibana@5.5.0 Running "esvm:test" (esvm) task

Elastic Stack Kibana
1

because Poor computer configuration.
i want to use the option : ES_JAVA_OPTS="-Xms512m -Xmx512m"
but the esvm seems to redownload the es everytime .so the option can't work because it was override.
Is there any option to let the esvm don't download and install everytime?

2

I think running with --esvm-no-fresh should accomplish what you're asking. Could you give it a try?

3

hey .it's work.but it look like my computer is very pool. even if ES_JAVA_OPTS="-Xms512m -Xmx512m"..it also doesn't work
and the warn is :

[root@zk1 kibana]$ npm run test --esvm-no-fresh
> kibana@5.5.0 test /home/ftpadmin/data/kibana
> grunt test

Running "test" task

Running "eslint:source" (eslint) task

Running "licenses" task

Running "checkPlugins" task

Running "esvm:test" (esvm) task
starting up "test" cluster
INFO -  - cluster - Downloading & installing from "5.5" branch.
INFO -  - cluster - Installing plugins
INFO -  - cluster - Purging /home/ftpadmin/data/kibana/esvm/test/branch-5.5/data
INFO -  - cluster - Starting 1 nodes
Warning: Command failed: /home/ftpadmin/data/kibana/esvm/test/branch-5.5/bin/elasticsearch -h
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000085330000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12)
 Use --force to continue.

Aborted due to warnings.

npm ERR! Linux 3.10.0-514.26.2.el7.x86_64
npm ERR! argv "/root/.nvm/versions/node/v6.10.2/bin/node" "/root/.nvm/versions/node/v6.10.2/bin/npm" "run" "test" "--esvm-no-fresh"
npm ERR! node v6.10.2
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! kibana@5.5.0 test: `grunt test`
npm ERR! Exit status 3
npm ERR! 
npm ERR! Failed at the kibana@5.5.0 test script 'grunt test'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the kibana package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs kibana
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls kibana
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/ftpadmin/data/kibana/npm-debug.log
4

Sorry, could you try adding an additional -- before the option, like this?

npm run test -- --esvm-no-fresh
5

thank you!it work!

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.