When I check the status of it with “sudo docker ps -a”, it has only been up for seconds.
When I check it with “sudo docker exec -it storagenode /app/dashboard.sh”, it shows the following error: “rpc: dial tcp 127.0.0.1:7778: connect: connection refused”
When I look at the logs with “sudo docker logs --tail 20 storagenode”, it shows the following 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”
I have no clue on what to do to get this working. Any help would be appreciated and please feel free to request any info needed to fix this.
If this is a new node - you missed the setup step. However, you must not run the setup step, if you called it once in the past for this identity.
If that was a worked node, then this is mean that the disk is dismounted. Please check the reason, why your disk is disappeared. You must not run a setup step in this case, otherwise you could destroy your node.
I ran the setup step already so I can’t run that again as you said.
The node has never worked, this is my first time joining as a Storj Node Operator.
The disk was mounted, I double checked.
Okay, so I started from scratch (new linux install, new identity created and authorized) so let’s forget all details for now and go through the setup process.
I just got to and ran the setup command and looked for errors after it ran.