no, you can put same as storage location, this is if you want to hold databases in separate place.
Hi there,
my second node just doesnât work and I donât know what it could be.
My identification worked, but I canât get it to work.
I have port 28967 for my main node and port 28968 for the second one.
I forwarded this with the FritzBox.
and the dsahboard didnât even start
Please help me
what is private address port? 7779?
seach logs for error in program Files/Storj1/Storagenode
what is toolbox version? 1.8 last?
HDD is over 500GB?
Hello Vadim,
thx for helping.
what is private address port? 7779?
127.0.0.1:7779
seach logs for error in program Files/Storj1/Storagenode
2021-01-18T13:25:10.795+0100 ERROR services unexpected shutdown of a runner {ânameâ: âpiecestore:monitorâ, âerrorâ: âpiecestore monitor: error verifying location and/or readability of storage directory: open D:\StorJ1\storage-dir-verification: Das System kann die angegebene Datei nicht finden.â, âerrorVerboseâ: âpiecestore monitor: error verifying location and/or readability of storage directory: open D:\StorJ1\storage-dir-verification: Das System kann die angegebene Datei nicht finden.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:131\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:128\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmoâ, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmoâ}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6â, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6â}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3Sâ, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3Sâ}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymBâ, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGEâ, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymBâ}
2021-01-18T13:25:10.796+0100 ERROR contact:service ping satellite failed {âSatellite IDâ: â12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDsâ, âattemptsâ: 1, âerrorâ: âping satellite error: rpc: dial tcp: operation was canceledâ, âerrorVerboseâ: âping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:106\n\tstorj.io/common/rpc.TCPConnector.DialContext:70\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:180\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:101\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:146\n\tstorj.io/common/rpc.Dialer.DialNodeURL:100\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGEâ}
2021-01-18T13:25:10.796+0100 INFO contact:service context cancelled {âSatellite IDâ: â12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDsâ}
2021-01-18T13:25:10.796+0100 ERROR nodestats:cache Get pricing-model/join date failed {âerrorâ: âcontext canceledâ}
2021-01-18T13:25:11.559+0100 FATAL Unrecoverable error {âerrorâ: âpiecestore monitor: error verifying location and/or readability of storage directory: open D:\StorJ1\storage-dir-verification: Das System kann die angegebene Datei nicht finden.â, âerrorVerboseâ: âpiecestore monitor: error verifying location and/or readability of storage directory: open D:\StorJ1\storage-dir-verification: Das System kann die angegebene Datei nicht finden.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:131\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:128\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57â}
what is toolbox version? 1.8 last?
The latest Version
HDD is over 500GB?
8TB HDD
is thes a local, connected by Sata cable hdd? it looks like it cant find storage directory normaly.
new hdd?
try to check D disk with checkdisk, i havent seen this error before.
Itâs not a new hard drive, Iâve had it for a long time, and itâs healthy. CrystalDiskInfo says all is well.
The hard drive is built into my server via SATA
your node is on I lable hdd, why it try write to D lable hdd?
i have cange now from D to I
you instaled new node by this, there was only needed to change path in config file
WOW
I changed the drive letter from D to I and now it works ⌠what the hell ⌠haha
THX Vadim !
you have 3 nodes now and second not work?
no, i have only now changed the drive letter.
Is there a tutorial or documentation for Toolbox? I plan to assemble a dedicated pc for Storj on three disks and I know that Win Toolbox allows me to create multiple nodes. Iâm not an expert and havenât found anything resembling âhelpââŚ
yes, here is one https://1stminingrig.com/how-to-host-a-storj-node-setup-earnings-reports/#How_to_add_new_HDD_to_Windows_Storj_Node_Hosting_Rig
Great! what I needed and (maybe) more!
idem donât work after upgrade to 1.21.1
This is related to the recent snoboard API changes.
Unfortunately some of the absolute numbers have been removed, which is really unfortunate. Though there was some suggestion in that topic that they may be added back.
If you want to help prevent such errors from appearing in community tools, I also suggest voting for this suggestion to implement API versioning.
Storagenode API versioning
I know @Vadim is really good about keeping things up to date, but the way it works now, anyone who built some tools for storage nodes can only really start fixing things when the release that breaks it is out in public.