zqd binary not present

[suricatalfon]

Hello,

sudo npm install:

(node:15643) UnhandledPromiseRejectionWarning: Error: zqd binary not present at /home/xxxx/install/brim/zdeps/zqd

Brim@0.5.4 build:css /home/alfon/install/brim
node-sass-chokidar src/css --output dist/css "--watch" "--skip-initial"

(node:16754) UnhandledPromiseRejectionWarning: Error: zqd binary not present at /home/alfon/install/brim/zdeps/zqd
at zqdCommand (/home/alfon/install/brim/dist/js/zqd/zqd.js:86:11)
at ZQD.start (/home/alfon/install/brim/dist/js/zqd/zqd.js:123:44)
at zqdMainHandler (/home/alfon/install/brim/dist/js/electron/ipc/zqd/mainHandler.js:12:9)
at _callee$ (/home/alfon/install/brim/dist/js/electron/main.js:69:42)
at tryCatch (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:45:40)
at Generator.invoke [as _invoke] (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:271:22)
at Generator.prototype. [as next] (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:97:21)
at asyncGeneratorStep (/home/alfon/install/brim/dist/js/electron/main.js:33:103)
at _next (/home/alfon/install/brim/dist/js/electron/main.js:35:194)
at /home/alfon/install/brim/dist/js/electron/main.js:35:364
(node:16754) UnhandledPromiseRejectionWarning: Error: zqd binary not present at /home/alfon/install/brim/zdeps/zqd
at zqdCommand (/home/alfon/install/brim/dist/js/zqd/zqd.js:86:11)
at ZQD.start (/home/alfon/install/brim/dist/js/zqd/zqd.js:123:44)
at zqdMainHandler (/home/alfon/install/brim/dist/js/electron/ipc/zqd/mainHandler.js:12:9)
at _callee$ (/home/alfon/install/brim/dist/js/electron/main.js:69:42)
at tryCatch (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:45:40)
at Generator.invoke [as _invoke] (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:271:22)
at Generator.prototype. [as next] (/home/alfon/install/brim/node_modules/regenerator-runtime/runtime.js:97:21)
at asyncGeneratorStep (/home/alfon/install/brim/dist/js/electron/main.js:33:103)
at _next (/home/alfon/install/brim/dist/js/electron/main.js:35:194)
at /home/alfon/install/brim/dist/js/electron/main.js:35:364
(node:16754) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16754) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:16754) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:16754) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Best regards,

[philrz]

@suricatalfon: Thanks for trying Brim & for the bug report.

After your report, I tried to reproduce the issue and that did lead us to quickly find & fix a problem that would have resulted in an error like you saw (#525). I can't say with 100% certainty that there's not another bug lurking in there, but could you try pulling the latest master of the Brim repo and attempt the npm install / npm start again?

If that doesn't fix it, it would help us to have a bit more info.

• First, what OS/version are you attempting this on? If it's Linux, please also provide the distro and version. Also please send the output of node --version.

• Next, I think your debug output might have been truncated a bit, as the error you pasted is what I'd expect to see during the npm start, not the npm install as your paste implied. If you try with the latest master and it still doesn't work, could you send us the full output of npm install & npm start? If there's sensitive info in there that you don't feel comfortable including in a public issue like this one, you could email it to us at support@brimsecurity.com or you could join our public Slack and start a private 1-on-1 with me (I'm @phil) on there.

Hope to hear from you soon.

[suricatalfon]

Thanks @philrz

It already works correctly. I think there was a mistake of mine too. I tried to run brim with sudo npm start instead of npm start.

(Sorry for my bad english).

Tranks ;-)
Best regards,

[philrz]

Thanks for the update @suricatalfon. I'll go ahead and close this one then.