for my opinion, this is bug in installer, if you choose not default port, it shold give to choose it, because, most people dont know if you choose other port you need to go to config file and change server.address: :43000, documentation also dont cover this part.
1 Like
You need to update the server.address in the config.yaml only if you forward to a different port.
If you setup the next node on different machine, you should use a different external port, but the default internal, i.e. forward 28968 to 28967. In this case you need to use this new external port only in contact.external-address: option.
2 Likes
Hallo,
ich habe mir die ToolBox heruntergeladen jedoch habe ich nun lediglich eine Art Dashboard. Wo bzw. wie kann ich dort jetzt eine weitere Festplatte zu meinem Node hinzufĂźgen?
It wold be good in English, other way no one understand the question.
âHello,
I downloaded the ToolBox but now I only have a kind of dashboard. Where or how can I add another hard drive to my node there nowâ
AFAIK it remains one drive per node. You can run multiple nodes but it is typically a good idea to come close to filling the first drive before starting a new node. Assuming you have a single IP.
2 Likes
Truly it much better to make separate nodes, as if you have one hdd broken, you will lose only 1 node. toolbox is only give possibilities, to install several nodes on single windows pc.
hello
I cant run 2nd node with toolbox, i think it comes down to toolbox is not running in administrator, ive ticked all premission boxes to allow to do so but still when i click stop or run node it says try to run in admin⌠windows10âŚthis is the error it generates
2022-10-25T19:08:48.903+0100 INFO Private server started on 127.0.0.1:7779
2022-10-25T19:08:49.524+0100 INFO trust Scheduling next refresh {âafterâ: â5h8m23.756245245sâ}
2022-10-25T19:08:49.524+0100 INFO bandwidth Performing bandwidth usage rollups
2022-10-25T19:08:49.530+0100 ERROR services unexpected shutdown of a runner {ânameâ: âpiecestore:monitorâ, âerrorâ: âpiecestore monitor: error verifying location and/or readability of storage directory: read E:\storj\storage-dir-verification: The handle is invalid.â, âerrorVerboseâ: âpiecestore monitor: error verifying location and/or readability of storage directory: read E:\storj\storage-dir-verification: The handle is invalid.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:133\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:130\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2022-10-25T19:08:49.530+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmoâ, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.530+0100 INFO contact:service context cancelled {âSatellite IDâ: â12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmoâ}
2022-10-25T19:08:49.531+0100 ERROR piecestore:cache error during init space usage db: {âerrorâ: âpiece space used: context canceledâ, âerrorVerboseâ: âpiece space used: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).Init:73\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:81\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2022-10-25T19:08:49.532+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGEâ, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.532+0100 INFO contact:service context cancelled {âSatellite IDâ: â1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGEâ}
2022-10-25T19:08:49.532+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6â, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.532+0100 INFO contact:service context cancelled {âSatellite IDâ: â121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6â}
2022-10-25T19:08:49.532+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3Sâ, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.532+0100 INFO contact:service context cancelled {âSatellite IDâ: â12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3Sâ}
2022-10-25T19:08:49.533+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymBâ, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.533+0100 INFO contact:service context cancelled {âSatellite IDâ: â12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymBâ}
2022-10-25T19:08:49.533+0100 ERROR nodestats:cache Get pricing-model/join date failed {âerrorâ: âcontext canceledâ}
2022-10-25T19:08:49.534+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDsâ, âattemptsâ: 1, âerrorâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite: rpc: tcp connector failed: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189â}
2022-10-25T19:08:49.534+0100 INFO contact:service context cancelled {âSatellite IDâ: â12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDsâ}
2022-10-25T19:08:49.536+0100 ERROR gracefulexit:blobscleaner couldnât receive satelliteâs GE status {âerrorâ: âcontext canceledâ}
2022-10-25T19:08:49.784+0100 FATAL Unrecoverable error {âerrorâ: âpiecestore monitor: error verifying location and/or readability of storage directory: read E:\storj\storage-dir-verification: The handle is invalid.â, âerrorVerboseâ: âpiecestore monitor: error verifying location and/or readability of storage directory: read E:\storj\storage-dir-verification: The handle is invalid.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:133\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:130\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
Hello.
This indicate that for some reason it not installed it properly.
try to delete it and reinstal, but you need to deinstall service first and not forget to delete also in program files. can you show conf how did you instaled it and version of toolbox?
1 Like
for uninstall service in cmd as admin, type sc.exe delete storagenode1
if it second node?
1 Like
Thank you, deleted it and reinstall and works perfectly! Not sure what happened
I managed to break the toolbox completely for installing new nodes after moving my logs and other files to a different location. The indexing for adding a new node is broken and will overwrite existing nodes files.
I am just manually making the new nodes now and using setup command to create the required verification file.
try to delete all nodes from toolbox, and click search, then it will fins allexisting nodes.
We need a youtube video on how toolbox works and how to add several nodes into it.
3 Likes
First of all, thank the creator of this tool.
I think that a guide or tutorial would be very good and would help reduce the number of reported problems.
but first of all thank you
1 Like
Hello and many thanks for the Tool.
I tried to create a new node with this tool.
But I have the following errors (see picture).
Here is the Logfile if I try to start the service:
2022-11-29T20:08:00.865+0100 INFO Configuration loaded {âLocationâ: âC:\Program Files\Storj1\Storage Node\config.yamlâ}
2022-11-29T20:08:00.877+0100 INFO Anonymized tracing enabled
2022-11-29T20:08:00.877+0100 INFO Operator email {âAddressâ: âo @googlemail.comâ}
2022-11-29T20:08:00.878+0100 INFO Operator wallet {âAddressâ: â0x04D9b86c893F 3B98d9e7E3C6D6d798â}
2022-11-29T20:08:01.055+0100 FATAL Unrecoverable error {âerrorâ: âError starting master database on storagenode: group:\nâ CreateFile E:\blobs: The system cannot find the file specified.\nâ CreateFile E:\temp: The system cannot find the file specified.\nâ CreateFile E:\garbage: The system cannot find the file specified.\nâ CreateFile E:\trash: The system cannot find the file specified.â, âerrorVerboseâ: âError starting master database on storagenode: group:\nâ CreateFile E:\blobs: The system cannot find the file specified.\nâ CreateFile E:\temp: The system cannot find the file specified.\nâ CreateFile E:\garbage: The system cannot find the file specified.\nâ CreateFile E:\trash: The system cannot find the file specified.\n\tmain.cmdRun:195\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:92\n\tstorj.io/private/process.ExecWithCustomConfig:74\n\tstorj.io/private/process.Exec:64\n\tmain.(*service).Execute.func1:61\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75â}
Does anyone other had this error and could fix it?
Thanks for help,
Oliver
what version of toolbox do you have?
did you signed identitie with new key from storj?
Hi, wow, fast response 
This is my version 1.8 from 5.1.2022
And yes, I created a new certificate for storenode1 (storenode is my main) with:
identity create storagenode1
And all steps on this side:
Iâm wondering about this path here:
Where dows it come from?
Storgenode1 is in âC:\Program Files\Storj1\Storage Nodeâ
The Tool is in âC:_Tools\Storj_add_Nodesâ
Somewhere it should be mixed?
Yes it looks like something is wrong.
I would use for identity C:\identity1, do not use long paths with spaces
I think when you installed something gone wrong, and it not created necessary folders in data hdd
you can delete is and install new one.
for this you need in cmd as admin write sc.exe delete storagenode1
then delete folder in program files storj1
and delete it from toolbox also
then make fresh install
for identity use C:\Identity1 and copy identity files there
My experience is that it works best if you leave all the node and id path settings at default. So ID and node is created in the c:\program files directory. Of course you should set the storage dir/drive, as you would like to have it. As soon as the node is created, you can move the ID and config files to the storage drive and edit the config.yaml.
When I wanted to set up the node to its final directory, it never worked. When I set it up with the defaults, it allways worked.
