Add existing Node's to multinode dashboard

[1arrcy1]

Im having issues finding the API key for my nodes, im currently on this screen and want to add 5 existing nodes split on multiple hosts, how would i approach this. Documentation is limited

[nerdatwork]

@1arrcy1

Documentation is limited

[Tech Preview] Multinode Dashboard Binaries

Testfocus We published the first binaries for the multinode dashboard on Github Release v1.34.3 · storj/storj · GitHub. Please test them and let us know if you have any issues. The main objective of this test is to find out if the binaries are working on different operating systems and setups. If you are able to add a storage node and can see it on the multinode dashboard I would call that success. We can also start to look for some wrong numbers on any of the pages. For example, the payout pag…

[1arrcy1]

just found it
docker exec -it storagenode6 /app/storagenode issue-apikey --config-dir config --identity-dir identity

Multinode docker 2024 howto

I decided to run the multinode dashboard to get a clearer picture of my storagenodes. So here is the howto Make a multinode dashboard First, this is linux I don’t understand windows, so make a folder for multinode. mkdir -p /multinode/identity and make config folder too. Create an identity the usual way (but for an easier size if you want to and no need to sign) Put the identity files in /multinode/identity/ Now run the docker multinode docker run -d --restart unless-stop…

getting tired IG its late for me

[LrrrAc]

Ive been trying to get an API key (finally found where storagenode is located), and this command completes without error, or output.

[Alexey]

You may try to add an option --log.output=stdout and, perhaps --log.level=info, if you have it on warn or error in your config file.

docker exec -it storagenode /app/bin/storagenode info --identity-dir identity --config-dir config --log.output=stdout --log.level=info

[LrrrAc]

That got me output, but now after it loads the config and identity, it gives an error that it cant directory lock filestatcache. Does badger need to be turned off for this?

[agente]

Yes. You have to disable it

[Alexey]

Ok, then you need to add another one flag --pieces.file-stat-cache="" to the command to temporary disable a badger cache only for that command.

[LrrrAc]

That did it! My working command was

sudo docker exec -it storagenode config/bin/storagenode issue-apikey --config-dir config --identity-dir identity --pieces.file-stat-cache=“”

Very different from the last time i tried the MND.

[Alexey]

Yes, but you have changed your config since then, right?

[LrrrAc]

I added the badger cache, but IDK how i could change where “storagenode” is located. That used to be /app/storagenode. Also the issue-apikey command used to output the node ID, now I found that “info” does that.

[Alexey]

You may mount a different source to the /app/storage/filestatcache in the container for the badger cache.
The new location for binaries now should be /app/bin/ runtime and the storage is /app/config/bin/. But it is for a latest image, if your run an outdated image, the binary would be in /app/.

[LrrrAc]

Then I think the solution to this thread is out of date.