Web dashboard is offline

Node Operators troubleshooting
1

Hello,

After latest update my web dashboard is not reachable anymore. The node itself is reachable, port 14002 is open. I see that it is in lisatening status on linux. I tried to reinstall the node again but still same issue. I have no more ideas where to look. Could someone help? I will provide info required for the troubleshooting.

BR,
Alex

2

Hello @Eridanin ,
Welcome to the forum!

The dashboard is listening on 127.0.0.1 by default, so you may open it only on the host.
To connect from other machines you need to use either How to remote access the web dashboard | Storj Docs or [Tech Preview] Multinode Dashboard Binaries

However, please check your logs first: How do I check my logs? | Storj Docs

3

I checked the logs. It is faling to start. I didn’t changed location of the DBs. It seems to happen after last update. Can it be solved?

2022-07-27 20:43:42,229 INFO Set uid to user 0 succeeded
2022-07-27 20:43:42,231 INFO RPC interface ‘supervisor’ initialized
2022-07-27 20:43:42,232 INFO supervisord started with pid 1
2022-07-27 20:43:43,234 INFO spawned: ‘processes-exit-eventlistener’ with pid 11
2022-07-27 20:43:43,234 INFO spawned: ‘storagenode’ with pid 12
2022-07-27 20:43:43,235 INFO spawned: ‘storagenode-updater’ with pid 13
2022-07-27T20:43:43.250Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.encoding”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2022-07-27T20:43:43.250Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.stack”}
2022-07-27T20:43:43.250Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.59.1”}
2022-07-27T20:43:43.250Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2022-07-27T20:43:43.250Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2022-07-27T20:43:43.250Z INFO Operator email {“Process”: “storagenode”, “Address”: “e3eridani@protonmail.com”}
2022-07-27T20:43:43.251Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0x322ca03488Baf7fcdeB307cF315a4F155578F643”}
Error: Error starting master database on storagenode: database: piece_spaced_used opening file “config/storage/piece_spaced_used.db” failed: unable to open database file: no such file or directory
storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:324
storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:306
storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:281
storj.io/storj/storagenode/storagenodedb.OpenExisting:248
main.cmdRun:193
storj.io/private/process.cleanup.func1.4:372
storj.io/private/process.cleanup.func1:390
github.com/spf13/cobra.(*Command).execute:852
github.com/spf13/cobra.(*Command).ExecuteC:960
github.com/spf13/cobra.(*Command).Execute:897
storj.io/private/process.ExecWithCustomConfigAndLogger:93
main.main:479
runtime.main:255
2022-07-27 20:43:43,281 INFO exited: storagenode (exit status 1; not expected)

4

Seems you have lost a database

You can use this guide to re-create it: https://support.storj.io/hc/en-us/articles/4403032417044-How-to-fix-database-file-is-not-a-database-error

5

well, the files are there, nothing is lost.

I tried to recreate as you recomended. It created .db files and then gives the same error (now output with other .db file)

2022-07-27T21:18:56.482Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.59.1”}
2022-07-27T21:18:56.482Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2022-07-27T21:18:56.485Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.59.1”}
2022-07-27T21:18:56.485Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2022-07-27 21:18:57,487 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-07-27 21:18:57,488 INFO spawned: ‘storagenode’ with pid 53
2022-07-27 21:18:57,488 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-07-27T21:18:57.508Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2022-07-27T21:18:57.509Z INFO Operator email {“Process”: “storagenode”, “Address”: “e3eridani@protonmail.com”}
2022-07-27T21:18:57.509Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0x322ca03488Baf7fcdeB307cF315a4F155578F643”}
Error: Error starting master database on storagenode: database: bandwidth opening file “config/storage/bandwidth.db” failed: unable to open database file: no such file or directory
storj.io/storj/storagenode/storagenodedb.(*DB).openDatabase:324
storj.io/storj/storagenode/storagenodedb.(*DB).openExistingDatabase:306
storj.io/storj/storagenode/storagenodedb.(*DB).openDatabases:281
storj.io/storj/storagenode/storagenodedb.OpenExisting:248
main.cmdRun:193
storj.io/private/process.cleanup.func1.4:372
storj.io/private/process.cleanup.func1:390
github.com/spf13/cobra.(*Command).execute:852
github.com/spf13/cobra.(*Command).ExecuteC:960
github.com/spf13/cobra.(*Command).Execute:897
storj.io/private/process.ExecWithCustomConfigAndLogger:93
main.main:479
runtime.main:255
2022-07-27 21:18:57,513 INFO exited: storagenode (exit status 1; not expected)

6

Then it maybe a permission issue. If you added a --user option to your docker run command then please change the owner to your user recursively and grant rwx access rights to you user recursively for the data location. You also should add your user to the docker group and relogin before run the container.

sudo usermod -aG docker $(id -un)

Then logout and login back to apply the change.
Then replace the owner and grant an access to your user:

sudo chown $(id -un):$(id -gn) -R /mnt/storj/storagenode
sudo chmod u+rwx -R /mnt/storj/storagenode