Start Node with old identity

Node Operators troubleshooting
1

I would like to know how do i start a node with a old identity? At starting there’s the output:

sudo docker run -d --restart always --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 127.0.0.1:14002:14002 -e WALLET="0x20Ba0Ed29B38F63CFe96193B1e85365821a7058221" -e EMAIL="tcarvalho5@gmail.com" -e ADDRESS="storagewars.dd.net:28967" -e STORAGE="2TB" --memory=800m --log-opt max-size=50m --log-opt max-file=10 --mount type=bind,source=home/storagewars/HDs/HD1/ID2/,destination=/app/identity --mount type=bind,source=home/storagewars/HDs/HD1,destination=/app/config --name storagenode storjlabs/storagenode:latest --operator.wallet-features: zksync-era
docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: 'home/storagewars/HDs/HD1/ID2/' mount path must be absolute.
See 'docker run --help'.


storagewars@raspberrypi:~ $ cd HDs
storagewars@raspberrypi:~/HDs $ cd HD1
storagewars@raspberrypi:~/HDs/HD1 $ ls
config.yaml  lost+found  retain          storage            trust-cache.json
ID2          orders      revocations.db  trust-cache1.json
storagewars@raspberrypi:~/HDs/HD1 $
2

Why would you want to use old identity ?

3

Node crashed a few days. I’m risking suspension! fFormated sd card and try to make it a go!

4

as the error says, you have a typo in the path

5

i know what it says! how do i fix it? since the path is correct?

docker run -d --restart always --stop-timeout 300 \
-p 28967:28967/tcp \
-p 28967:28967/udp \
-p 127.0.0.1:14002:14002 \
-e WALLET="0x20Ba0Ed29B38F63CFe96193B1e85365821a7058a" \
-e EMAIL="tcarvalho85@gmail.com" \
-e ADDRESS="storagewars.ddns.net:28967" \
-e STORAGE="2TB" \
--memory=800m \
--log-opt max-size=50m \
--log-opt max-file=10 \
--mount type=bind,source=home/storagewars/HDs/HD1/ID2,destination=/app/identity \
--mount type=bind,source=home/storagewars/HDs/HD1,destination=/app/config \
--name storage storjlabs/storagenode:latest
--operator.wallet-features=zksync-era

Update 1
Changed ID directory

storagewars@raspberrypi:~ $ sudo docker run -d --restart always --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 127.0.0.1:14002:14002 -e WALLET="0x20Ba0Ed29B38F63CFe96193B1e85365821a7058a" -e EMAIL="tcarvalho85@gmail.com" -e ADDRESS="storagewars.ddns.net:28967" -e STORAGE="2TB" --memory=800m --log-opt max-size=50m --log-opt max-file=10 --mount type=bind,source=/home/storagewars/IDNode1,destination=/app/identity --mount type=bind,source=home/storagewars/HDs/HD1,destination=/app/config --name storage storjlabs/storagenode:latest --operator.wallet-features: “zksync-era”
docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: 'home/storagewars/HDs/HD1' mount path must be absolute.
See 'docker run --help'.

Issue2
Issue21920×1080 299 KB

6

Try this

--mount type=bind,source=/home/storagewars/HDs/HD1/ID2,destination=/app/identity \
--mount type=bind,source=/home/storagewars/HDs/HD1,destination=/app/config \
2 Likes
7

I think that’s because on GUI you can see 2.0 Volume and on CLI you only see HD1.

8 
2025-02-16T16:59:43Z	ERROR	pieces	used-space-filewalker failed	{"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Lazy File Walker": false, "error": "filewalker: used_space_per_prefix_db: context canceled", "errorVerbose": "filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:96\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:83\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:783\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-02-16T16:59:43Z	ERROR	piecestore:cache	encountered error while computing space used by satellite	{"Process": "storagenode", "error": "filewalker: used_space_per_prefix_db: context canceled", "errorVerbose": "filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:96\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:83\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:783\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78", "SatelliteID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"}
2025-02-16T16:59:43Z	ERROR	piecestore:cache	error getting current used space for trash: 	{"Process": "storagenode", "error": "filestore error: failed to walk trash namespace af2c42003efc826ab4361f73f9d890942146fe0ebe806786f8e7190800000000: context canceled", "errorVerbose": "filestore error: failed to walk trash namespace af2c42003efc826ab4361f73f9d890942146fe0ebe806786f8e7190800000000: context canceled\n\tstorj.io/storj/storagenode/blobstore/filestore.(*blobStore).SpaceUsedForTrash:302\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:105\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
2025-02-16T16:59:44Z	ERROR	failure during run	{"Process": "storagenode", "error": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open config/storage/storage-dir-verification: no such file or directory\n\tstorj.io/storj/storagenode/monitor.(*Service).verifyStorageDir:161\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:109\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}
Error: piecestore monitor:

error verifying location and/or readability of storage directory: 

open config/storage/storage-dir-verification: no such file or directory
9

missing " at source!!!

--mount type=bind,source="<identity-dir>",destination=/app/identity
1 Like
10

2025-02-16T17:31:34Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2025-02-16T17:31:34Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
Error: storagenode configuration already exists (/app/config)

11
12

Several times you use relative paths instead of absolute paths. The leading / makes a big difference.

13

I’ve noticed a slash can make a huge difference!

14

Does this file "/home/storagewars/HDs/2.0 TB Volume/storage/storage-dir-verification" exist?

ls -l "/home/storagewars/HDs/2.0 TB Volume/storage/storage-dir-verification"

Does this file "/home/storagewars/HDs/HD1/storage/storage-dir-verification" exist?

ls -l "/home/storagewars/HDs/HD1/storage/storage-dir-verification"

If the first is exist, but the second - not, then perhaps you need to replace

with

--mount type=bind,source="/home/storagewars/HDs/2.0 TB Volume/ID2",destination=/app/identity \
--mount type=bind,source="/home/storagewars/HDs/2.0 TB Volume",destination=/app/config \

Please show the result of the command:

ls -l /home/storagewars/HDs