The node resets every 30 seconds and does not start up

Node Operators troubleshooting
,
1

hello. i have a node installed, however it restarts every 30 seconds.
i have already reinstalled everything. However no improvement.

I use the following string to start:

docker run -d --restart unless-stopped -p 28967:28967/tcp -p 28967:28967/udp -p 192.168.24.14:14002:14002 -e WALLET=“0x0xxxxxx” -e EMAIL=“xxx” -e ADDRESS=“xxx.zapto. org:28967” -e BANDWIDTH=“22TB” -e STORAGE=“8790GB” --mount type=bind,source=“/home/administrator/.local/share/storj/identity/storagenode1”,destination=/app/identity --mount type=bind,source=“/mnt/edrive1”,destination=/app/config --name storagenode1 storjlabs/storagenode:latest

Ports and port forwarding is enabled and firewall configured in my opinion.

2

Have a look at this article on how access logs: How do I check my logs? - Storj Node Operator Docs

2 Likes
3

Hello thx, for the hint and i checked my logs…

Well, it’s the HD mounting? But I don’t know what I should change. The disks should be mounted and I also see a few directories on the HD. Or is it because of the name storagenode, because I use storagenode1 (background is that I have 2 nodes running on my Raspberry).

My Log…
$ docker logs --tail 20 storagenode1
2023-07-05 18:19:28,122 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-07-05T18:19:28.257Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-05T18:19:28.281Z INFO Operator email {“process”: “storagenode”, “Address”: “xxx@xxx.com”}
2023-07-05T18:19:28.281Z INFO Operator wallet {“process”: “storagenode”, “Address”: “0x3Bxxxx”}
Error: Error starting master database on storagenode: group:
— stat config/storage/blobs: no such file or directory
— stat config/storage/temp: no such file or directory
— stat config/storage/garbage: no such file or directory
— stat config/storage/trash: no such file or directory
2023-07-05 18:19:28,290 INFO exited: storagenode (exit status 1; not expected)
2023-07-05 18:19:30,301 INFO spawned: ‘storagenode’ with pid 54
2023-07-05T18:19:30.500Z INFO Anonymized tracing enabled {“process”: “storagenode”}
2023-07-05T18:19:30.526Z INFO Operator email {“process”: “storagenode”, “Address”: “xxx@xxx.com”}
2023-07-05T18:19:30.526Z INFO Operator wallet {“process”: “storagenode”, “Address”: “0x3Bxxxxx”}
Error: Error starting master database on storagenode: group:
— stat config/storage/blobs: no such file or directory
— stat config/storage/temp: no such file or directory
— stat config/storage/garbage: no such file or directory
— stat config/storage/trash: no such file or directory
2023-07-05 18:19:30,534 INFO exited: storagenode (exit status 1; not expected)

Thx

4

if this is a new identity (I.e. new node), then you missed the setup step.

5

After a longer look, you were absolutely right. I immediately mistook the first step for the second. I deleted the directories again; remounted and reconfigured. Step 1 and 2. now everything works. Problem solved. Thank you very much.

1 Like
6

And you are right too - you should skip the setup step anytime later, if it’s have been performed once for that identity.
This step creates a folder structure and generates a check file storage-dir-verification with encoded identity of this node. This file will protect your node from disqualification in cases if your drive is unmounted for any reason or you provided a wrong identity, or a wrong data location.

However, if you perform a setup step in the second time with a wrong path or a wrong identity, your protection will be overridden and node could be disqualified.