[Tech Preview] Storage Node Multinode Dashboard

Thank you very much for your feedback. I will address that and maybe the team has an idea to make that a bit more clear which port to pick.

4 Likes

Hello
Tried to set it up on my Ubuntu 20.04 and I must admit I am not master of npm etc but pls read below errors encountered upon trying and setting up (first block of instructions)
how do I “install peer dependencies myself” as WARN messages tell me to do?
tahank you in advance!

nicolas@nicolas-VirtualBox:~/multinode/web/multinode$ npm install
npm WARN @fimbul/bifrost@0.21.0 requires a peer of tslint@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @vue/cli-plugin-typescript@4.5.9 requires a peer of @vue/compiler-sfc@^3.0.0-beta.14 but none is installed. You must install peer dependencies yourself.
npm WARN @vue/cli-service@4.5.9 requires a peer of @vue/compiler-sfc@^3.0.0-beta.14 but none is installed. You must install peer dependencies yourself.
npm WARN sass-loader@8.0.0 requires a peer of node-sass@^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN sass-loader@8.0.0 requires a peer of fibers@>= 3.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN tslint-consistent-codestyle@1.16.0 requires a peer of tslint@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN multinode@0.0.1 No description
npm WARN multinode@0.0.1 No repository field.
npm WARN multinode@0.0.1 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fork-ts-checker-webpack-plugin-v5@npm:fork-ts-checker-webpack-plugin@5.2.1 (node_modules/fork-ts-checker-webpack-plugin-v5):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Invalid dependency type requested: alias
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: vue-loader-v16@npm:vue-loader@16.1.2 (node_modules/vue-loader-v16):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Invalid dependency type requested: alias
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
audited 1580 packages in 87.467s
found 0 vulnerabilities
nicolas@nicolas-VirtualBox:~/multinode/web/multinode$ npm run build
multinode@0.0.1 build /home/nicolas/multinode/web/multinode
vue-cli-service build
ERROR Error loading /home/nicolas/multinode/web/multinode/vue.config.js:
ERROR SyntaxError: Unexpected reserved word
/home/nicolas/multinode/web/multinode/node_modules/stylelint/node_modules/cosmiconfig/dist/Explorer.js:54
for await (const place of this.config.searchPlaces) {
^^^^^
SyntaxError: Unexpected reserved word
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions…js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/home/nicolas/multinode/web/multinode/node_modules/stylelint/node_modules/cosmiconfig/dist/index.js:12:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! multinode@0.0.1 build: vue-cli-service build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the multinode@0.0.1 build 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! /home/nicolas/.npm/_logs/2021-02-25T13_18_30_335Z-debug.log
nicolas@nicolas-VirtualBox:~/multinode/web/multinode$

Try this:

npm version
npm install -g n
n lts
npm version

thanks and I was able to set it up (needed to sudo the n its, but went well, few warnings only)
however after creating identity successfully, the 3 multimode instructions end up as “multimode: command not found”…

multinode ?: commande introuvable

export PATH=$PATH:$HOME/go/bin

littleskunk always on fire, thanks for the support
unfortunately this did not go through
I had issues compiling as my go was too old, updated to latest version, compiled again all with few warnings :confused:

sounds like multimode is not recognised as an app, but identity was, and if I am not mistaken, identity is also go app?

which identity will tell you if it is running the identity binary in your go directory or from some other unexpected location. On my machine I have 3 different identity versions somewhere deep in my system. That can get confusing.

identity used is /usr/local/bin/identity

That is not the one you are currently compiling and it does mean that you will find the multinode binary in the path that I have written above.

thanks for your efforts @littleskunk but I believe I will give up now as not good enough in compiling stuff on Linux… will need to wait for a multimode dashboard for dummies" step by step tutorial. but much appreciated your support!

You are so close. You should have the binary already.

cd $HOME/go/bin

which go tells me /usr/local/go/bin/go
sounds like something is going wrong when compiling but to be noticed, in the listed

cd $HOME/multinode
go install ./cmd/multinode
go install ./cmd/identity
cd web/multinode
npm install
npm run build

I need to sudo the last npm run build and trust the issue comes from here as it seems I don’t have same path as su vs as std user

giving it another try, I get the below error when restarting all form beginning:

nicolas@inoc-node:~/multinode/web/multinode$ npm run build
multinode@0.0.1 build /home/nicolas/multinode/web/multinode
vue-cli-service build
ERROR Error loading /home/nicolas/multinode/web/multinode/vue.config.js:
ERROR SyntaxError: Unexpected reserved word
/home/nicolas/multinode/web/multinode/node_modules/stylelint/node_modules/cosmiconfig/dist/Explorer.js:54
for await (const place of this.config.searchPlaces) {
^^^^^
SyntaxError: Unexpected reserved word
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions…js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/home/nicolas/multinode/web/multinode/node_modules/stylelint/node_modules/cosmiconfig/dist/index.js:12:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! multinode@0.0.1 build: vue-cli-service build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the multinode@0.0.1 build 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! /home/nicolas/.npm/_logs/2021-02-27T08_33_12_830Z-debug.log

so git clone, go install multinode, go install identity npm install look fine (few warnings on npm install for optional dependencies skipped) and upon npm build, sh*tstorm starts with the above errors. running npm build as sudo allows setup to complete as success but multinode is not recognised as a valid command
and, not master of npm nor of go, but cannot really locate which file is considered exec/is go working like implicit go multinode when inputting multinode as an executable?

Hello,
It took me a while to follow instructions, more than 1 hour for zero result.
Finally build it on macosX, go it running, generated API Key for a node.
but unable to +New Node
Set Node ID; public IP in http://…:port ; API key
push create, nothing happens. nothing in logs.
Checked trice my inputs.
I also had to guess I needed to build storagenode go binary to generate api-key.
The storagenode container could be directly invoked in interactive mode.
Voila

That part is wrong. You have to insert ip:port only. Port should be the same port you have forwarded for the communication to the satellite.

Could someone upload compiled versions of multinode and npm folder? I’ve managed to compile multinode myself, but can’t cope with npm.

This is compiled static content
http://transfer.sh/iTSuB/multinode.tar.gz

1 Like