Error: Error starting master database on storagenode: group: stat config/storage/blobs: no such file or directory

I am starting a new node with new identity authorised. However, i come across this error:

2020-12-11T16:00:24.862274611Z 2020-12-11T16:00:24.861Z INFO Operator email {“Address”: “…”}
2020-12-11T16:00:24.862442607Z 2020-12-11T16:00:24.862Z INFO Operator wallet {“Address”: “…”}
2020-12-11T16:00:24.862857640Z Error: Error starting master database on storagenode: group:
2020-12-11T16:00:24.863006678Z — stat config/storage/blobs: no such file or directory
2020-12-11T16:00:24.863051010Z — stat config/storage/temp: no such file or directory
2020-12-11T16:00:24.863074635Z — stat config/storage/garbage: no such file or directory
2020-12-11T16:00:24.863096218Z — stat config/storage/trash: no such file or directory<

what could have possibly gone wrong?

1 Like

Before the start you need to setup the node: https://documentation.storj.io/setup/cli/storage-node#setting-up-the-storage-node
This change has been made to protect your old node from the disqualification, if your storage is gone for any reason.

3 Likes

[root@localhost storj]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5725257fcbf9 storjlabs/storagenode:latest “/entrypoint” 3 minutes ago Restarting (1) 17 seconds ago storagenode
[root@localhost storj]# docker logs storagenode
2020-12-12T14:12:14.872Z INFO Operator email {“Address”: “xxx@gmail.com”}
2020-12-12T14:12:14.872Z INFO Operator wallet {“Address”: “xxx”}
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 the same problem.

I have tried it, but it didn’t work.

Hello @ori,
Welcome to the forum!

What the command you have tried and what is it showed?

docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967
-p 14002:14002
-e WALLET=“xxx”
-e EMAIL="xxx@gmail.com"
-e ADDRESS=“134.195.89.2:28967”
-e BANDWIDTH=“7.5TB”
-e STORAGE=“8.8TB”
–mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/root/storj/",destination=/app/config
–name storagenode storjlabs/storagenode:latest

it will definitely fail, if you didn’t run your node with a -e SETUP=true option first, as described there:

https://documentation.storj.io/setup/cli/storage-node#setting-up-the-storage-node

docker run --rm -e SETUP=“true”
–mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/root/storj/",destination=/app/config
–name storagenode storjlabs/storagenode:latest

I did this before.

The path was wrong, and it has been resolved. Thank you!

1 Like

A post was merged into an existing topic: X509: certificate signed by unknown authority for https://tardigrade.io/trusted-satellites

3 posts were merged into an existing topic: QNAP StorJ_1.1.0 Nothing works, no response

I have a same issue. Over the couple of years installed storj many times with no problems. Yesterday stuck at the same place. Tried to find solution here in forum, but could not :expressionless:

If i run setup, get this:

node4@node4:~ $ docker run --rm -e SETUP=“true” --mount type=bind,source="/home/node4/storj/4/cert4/",destination=/app/identity --mount type=bind,source="/home/node4/storj/4/data4",destination=/app/config --name storagenode4 storjlabs/storagenode:latest
2021-05-03T10:06:52.071Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
Error: storagenode configuration already exists (/app/config)

If try to run the node, it did not:

node4@node4:~/storj docker run -d --restart unless-stopped --stop-timeout 300 -p 28967:28967 -p 127.0.0.1:14002:14002 -e WALLET=“xxxxxxxxxx” -e EMAIL=“xxxxxxxxx" -e ADDRESS="xxxxxxxxx:28967" -e STORAGE="800GB" --mount type=bind,source="/home/node4/storj/4/cert4/",destination=/app/identity --mount type=bind,source="/home/node4/storj/4/data4",destination=/app/config --name storagenode4 storjlabs/storagenode:latest 6bdc1c9a52f7fe74115764996914f3ad23b516875b5b494bbc51697474e96869 node4@node4:~/storj docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6bdc1c9a52f7 storjlabs/storagenode:latest “/entrypoint” 23 seconds ago Restarting (1) 9 seconds ago storagenode4
node4@node4:~/storj docker logs -f --tail 40 storagenode4 2021-05-03T00:23:48.202Z INFO Operator email {"Address": "xxxxx"} 2021-05-03T00:23:48.203Z INFO Operator wallet {"Address": "xxxxx"} 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 2021-05-03T00:24:01.978Z INFO Operator email {"Address": "xxxxx"} 2021-05-03T00:24:01.978Z INFO Operator wallet {"Address": "xxxxx"} 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 2021-05-03T00:24:11.572Z INFO Operator email {"Address": "xxxxx"} 2021-05-03T00:24:11.573Z INFO Operator wallet {"Address": "xxxxx"} 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 2021-05-03T00:24:23.904Z INFO Operator email {"Address": "xxxxx"} 2021-05-03T00:24:23.904Z INFO Operator wallet {"Address": "xxxxx"} 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 node4@node4:~/storj

I even tried manually create those folders, but it did not helped.

@Alexey looks like your consultation is needed again :slight_smile:

Thank you.

You have /home/node4/storj/4/data4/config.yaml already, please, remove it first.

The storage must be empty for a new node. This is for protection of your earnings, if you run the setup by mistake in the second time. So, you should understand what are you doing and as a last resort to fail, if config file already exist.

I also have this error. I’m using Oracle Linux 9.

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’ve tried stopping then removing the docker container and re-running the update command. I’m running as root but ran as a user the first time. I’ve double checked my paths. Podman was installed from dnf. The machine is a VM on a Synology NAS. I’ve run sealert -l “*” a bunch of times and cleared out any related selinux issues. Not sure what to try next.

Thanks for your help :slight_smile:

Scott

Hello @storescott,
Welcome to the forum!

Why do not run docker directly on Synology?

Please show your mount options in your podman run command, and result of this command:

df -T --si

Is it a new node or worked one?

Great question. I was looking for isolation from my network and thought this would be the best way but I suppose I could setup the docker container to only use an isolated network port too? Do you recommend any specific synology instructions?

I’m setting up a brand new node.

Filesystem                  Type      Size  Used Avail Use% Mounted on
devtmpfs                    devtmpfs  4.2M     0  4.2M   0% /dev
tmpfs                       tmpfs     1.6G  173k  1.6G   1% /dev/shm
tmpfs                       tmpfs     619M   69M  551M  12% /run
/dev/mapper/ol_snape-root   xfs        72G   13G   60G  18% /
/dev/sdb1                   xfs       1.1G  508M  556M  48% /boot
/dev/mapper/ol_snape-home   xfs        35G  502M   35G   2% /home
/dev/mapper/storage-storage ext4       11T   29k  9.7T   1% /mnt/storage
tmpfs                       tmpfs     310M   50k  310M   1% /run/user/1000
shm                         tmpfs      66M     0   66M   0% /var/lib/containers/storage/overlay-containers/97f3b6efe6ac0fcd9d1bb5b00d67f8fbacbcade2bbe12b0d465bfbd32641a44a/userdata/shm
overlay                     overlay    72G   13G   60G  18% /var/lib/containers/storage/overlay/56a24ba1e7e18767147a50230b947ba5da7e2ffb1a6af522add959912dd9845c/merged

I have a container running on synology now, thanks. :slight_smile:

1 Like