Testing binary Killed

[metallicats]

Binary found at /root/Vector-Production/bundle/programs/server/npm/node_modules/meteor/appworkshop_materialize/node_modules/node-sass/vendor/linux-x64-57/binding.node
Testing binary
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! node-sass@4.5.3 postinstall: node scripts/build.js
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the node-sass@4.5.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-04-24T15_27_17_027Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR! meteor-dev-bundle@ install: node npm-rebuild.js
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the meteor-dev-bundle@ install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-04-24T15_27_17_229Z-debug.log
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: main.js

[bmcgonag]

I usually see ELIFECYCLE errors when running the node process as a user with not enough privileges. This has so far meant I have to run this as root (which I hate), but so far, haven't been able to get some of the commands in the application to run properly, not so much the install script, but for that reason I don't run the node parts with sudo in the script either.

Are you running as root user?

[metallicats]

Sorry, I left some incomplete Infos. Yes, I ran this with root access and also it's on a Google cloud vm. I didn't get this error when I installed it on Hetzner cloud. Which unfortunately gave me the next error where it wouldn't finish the handshake.

[bmcgonag]

I have updated the build to 0.5.0 and updated the framework for Meteor, which also comes with a jump from Node v7 to Node v 12.16.1. Would you mind pulling down the latest vector_install.sh script from the releases on 0.5.0, and trying it again?