The node is new, i have not been able to access the dashboard because the node restarts constantly.
I’m using Linux CLI with Docker. I have followed the official guide and have Mounted the drive prior to installing the node.
What can i do next?
First of all - read the log
Error: Error opening 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/trash: no such file or directory
Fist run must be with setup command to create folders. Did you?
-e SETUP="true"
Edit: I have run it because it’s part of the command on the official guide
unless this is part of the command from the official guide then no.
im also getting this in the logs: “/entrypoint: line 25: /app/config/bin/storagenode-updater: Permission denied”
this is the last 20 lines of the log: 14500K … … … … … 95% 74.0M 0s
14550K … … … … … 95% 72.5M 0s
14600K … … … … … 95% 70.0M 0s
14650K … … … … … 96% 92.4M 0s
14700K … … … … … 96% 68.2M 0s
14750K … … … … … 96% 75.9M 0s
14800K … … … … … 97% 82.6M 0s
14850K … … … … … 97% 56.8M 0s
14900K … … … … … 97% 60.2M 0s
14950K … … … … … 98% 83.3M 0s
15000K … … … … … 98% 78.1M 0s
15050K … … … … … 98% 67.9M 0s
15100K … … … … … 99% 85.4M 0s
15150K … … … … … 99% 73.4M 0s
15200K … … … … … 99% 78.3M 0s
15250K … … … … . 100% 80.3M=0.4s
2025-02-07 20:22:47 (41.1 MB/s) - ‘/tmp/storagenode-updater.zip’ saved [15658411/15658411]
/entrypoint: line 25: /app/config/bin/storagenode-updater: Permission denied
Check your paths. Check your permissions and owner. If all are OK for your user, running the setup should create those directories and a config.yaml file.
1 Like
Do you run docker with sudo?
1 Like
Hello @4lexjj11,
Welcome back!
If you use a --user option in your docker run command, then make sure that your user does have access to the data folder and the identity, if not, you likely need either to change the owner to your user for both the data and the identity locations to your user or remove the --user option and continue run with sudo.
1 Like
I have not run docker with Sudo.
The run command does use --user
I believe that the user has perms
this is the latest logs:
2025-02-08T13:44:01Z ERROR failure during run {“Process”: “storagenode”, “error”: “Error opening database on storagenode: group:\n— stat config/storage/blobs: no such file or directory\n— stat config/storage/temp: no such file or directory\n— stat config/storage/trash: no such file or directory”, “errorVerbose”: “Error opening database on storagenode: group:\n— stat config/storage/blobs: no such file or directory\n— stat config/storage/temp: no such file or directory\n— stat config/storage/trash: no such file or directory\n\tmain.cmdRun:69\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:272”}
Error: Error opening 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/trash: no such file or directory
2025-02-08 13:44:01,293 WARN exited: storagenode (exit status 1; not expected)
You should put your docker run command to be able to understand
1 Like
docker run --rm -e SETUP=“true” --user $(id -u):$(id -g) --mount type=bind,source=“/home/freebox/.local/share/storj/identity/storagenode”,destination=/app/identity --mount type=bind,source=“/mnt/storj”,destination=/app/config --name storagenode storjlabs/storagenode:latest
Just go to your node folder and check it with
ls -lh
If its not owned by the user runing the node use chown command to change
2 Likes
Please do not include this command to any script. It should be run only to setup a node for a first time for the same identity, it shouldn’t be used again for the working node.