I am getting this as error when i am trying to start my storage node
“2025-02-20T19:20:48Z ERROR services unexpected shutdown of a runner {“Process”: “storagenode”, “name”: “piecestore:monitor”, “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”}
2025-02-20T19:20:48Z ERROR gracefulexit:blobscleaner couldn’t receive satellite’s GE status {“Process”: “storagenode”, “error”: “context canceled”}
2025-02-20T19:20:48Z ERROR version failed to get process version info {“Process”: “storagenode”, “error”: “version checker client: Get "https://version.storj.io": context canceled”, “errorVerbose”: “version checker client: Get "https://version.storj.io": context canceled\n\tstorj.io/storj/private/version/checker.(*Client).All:68\n\tstorj.io/storj/private/version/checker.(*Client).Process:89\n\tstorj.io/storj/private/version/checker.(*Service).checkVersion:104\n\tstorj.io/storj/private/version/checker.(*Service).CheckVersion:78\n\tstorj.io/storj/storagenode/version.(*Chore).checkVersion:115\n\tstorj.io/storj/storagenode/version.(*Chore).RunOnce:71\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/storj/storagenode/version.(*Chore).Run:64\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78”}
2025-02-20T19:20:48Z ERROR nodestats:cache Get pricing-model/join date failed {“Process”: “storagenode”, “error”: “context canceled”}
2025-02-20T19:20:48Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 1, “error”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup eu1.storj.io: operation was canceled”, “errorVerbose”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup eu1.storj.io: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190”}
2025-02-20T19:20:48Z INFO contact:service context cancelled {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2025-02-20T19:20:48Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 1, “error”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup saltlake.tardigrade.io: operation was canceled”, “errorVerbose”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup saltlake.tardigrade.io: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190”}
2025-02-20T19:20:48Z INFO lazyfilewalker.trash-cleanup-filewalker subprocess exited with status {“Process”: “storagenode”, “satelliteID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “status”: -1, “error”: “signal: killed”}
2025-02-20T19:20:48Z INFO contact:service context cancelled {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2025-02-20T19:20:48Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 1, “error”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup us1.storj.io: operation was canceled”, “errorVerbose”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup us1.storj.io: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190”}
2025-02-20T19:20:48Z INFO contact:service context cancelled {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2025-02-20T19:20:48Z ERROR pieces:trash emptying trash failed {“Process”: “storagenode”, “error”: “pieces error: lazyfilewalker: signal: killed”, “errorVerbose”: “pieces error: lazyfilewalker: signal: killed\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*process).run:85\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*Supervisor).WalkCleanupTrash:196\n\tstorj.io/storj/storagenode/pieces.(*Store).EmptyTrash:486\n\tstorj.io/storj/storagenode/pieces.(*TrashChore).Run.func1.1:86\n\tstorj.io/common/sync2.(*Workplace).Start.func1:89”}
2025-02-20T19:20:48Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 1, “error”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup ap1.storj.io: operation was canceled”, “errorVerbose”: “ping satellite: rpc: tcp connector failed: rpc: dial tcp: lookup ap1.storj.io: operation was canceled\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190”}
2025-02-20T19:20:48Z INFO contact:service context cancelled {“Process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2025-02-20T19:20:48Z 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
2025-02-20 19:20:48,556 WARN exited: storagenode (exit status 1; not expected)
2025-02-20 19:20:49,560 INFO spawned: ‘storagenode’ with pid 123
2025-02-20 19:20:49,561 WARN received SIGQUIT indicating exit request
2025-02-20 19:20:49,562 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2025-02-20T19:20:49Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2025-02-20 19:20:49,570 INFO stopped: storagenode-updater (exit status 0)
2025-02-20 19:20:49,571 WARN stopped: storagenode (terminated by SIGTERM)
2025-02-20 19:20:49,572 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
root@das-simulations /usr/local/src/noip-2.1.9-1 #”
Please help me in resolving this error and setting up my node on virtual machine .
The error seems to indicate that your node can’t find a file called storage-dir-verification
That file is generated during the setup process. Did you run a setup command that looks like this?
docker run --rm -e SETUP="true" \
--user $(id -u):$(id -g) \
--mount type=bind,source="<identity-dir>",destination=/app/identity \
--mount type=bind,source="<storage-dir>",destination=/app/config \
--name storagenode storjlabs/storagenode:latest
No , do you have all set of commands through which i am able to run the stroage node on my system and i am using virtual machine which is hosted on cloud so for that is there any change of steps.
I’ve never tried that. Not sure.
Setup instructions linked below.
1 Like
why my QUIC is showing misconfigure and status of node as offline
even though i have configure firewall also
There cannot be any difference. Why would there be any?
You need to check step by step that ports are open on your VPS firewall, that your instance has public IP, that firewall on the instance allows the port. Depending on the instance configuration and provider rule sequencing may be important, depending on how you configure firewall. Basically, use any online port testing tool, and make sure your node’s port is accessible when the node is running.
Ignore QUIC, focus on getting online status first. QUIC may or may not end up working, but it’s irrelevant today.
Also please don’t post screenshots of logs, they are useless for all intents and purposes. If you want to share logs – share them in the body of the post between sets of ```, like so:
```
logs go here
```
will end up looking like so
logs go here
Please review this: Formatting posts using markdown, BBCode, and HTML - Using Discourse - Discourse Meta
2 Likes