Error when connecting to dashboard on Ubuntu 22

Node Operators troubleshooting
,
1

I try to connect or on the internal port(14002) and on the external port(28967) and the container crashes)
Output: sudo docker exec -it storagenode /app/dashboard.sh

2023-10-23T17:21:32Z    INFO    Configuration loaded    {"process": "storagenode", "Location": "/app/config/config.yaml"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.wallet-features"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.wallet"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "server.address"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "server.private-address"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "healthcheck.enabled"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.email"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "contact.external-address"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "storage.allocated-disk-space"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "version.server-address"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "healthcheck.details"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "storage.allocated-bandwidth"}
2023-10-23T17:21:32Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "console.address"}
2023-10-23T17:21:32Z    INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-10-23T17:21:32Z    INFO    Identity loaded.        {"process": "storagenode", "Node ID": "12Wh2jEx5vc23JMzQXHYvwUN21xmbcyQbvTBmrvNHmVM6qUNh7C"}
Error: manager closed: closed: read tcp 127.0.0.1:39552->127.0.0.1:7778: read: connection reset by peer

mimi@bravo-788:~$ sudo docker logs --tail 20 storagenode
2023-10-23T17:29:34Z    INFO    pieces:trash    emptying trash started  {"process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2023-10-23T17:29:34Z    ERROR   piecestore:cache        error during init space usage db:       {"process": "storagenode", "error": "piece space used: context canceled", "errorVerbose": "piece space used: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceSpaceUsedDB).Init:73\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:81\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:44\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-10-23T17:29:34Z    ERROR   nodestats:cache Get pricing-model/join date failed      {"process": "storagenode", "error": "context canceled"}
2023-10-23T17:29:34Z    ERROR   gracefulexit:blobscleaner       couldn't receive satellite's GE status  {"process": "storagenode", "error": "context canceled"}
2023-10-23T17:29:34Z    ERROR   collector       error during collecting pieces:         {"process": "storagenode", "error": "pieceexpirationdb: context canceled", "errorVerbose": "pieceexpirationdb: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*pieceExpirationDB).GetExpired:39\n\tstorj.io/storj/storagenode/pieces.(*Store).GetExpired:571\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:88\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:44\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-10-23T17:29:34Z    ERROR   gracefulexit:chore      error retrieving satellites.    {"process": "storagenode", "error": "satellitesdb: context canceled", "errorVerbose": "satellitesdb: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*satellitesDB).ListGracefulExits:192\n\tstorj.io/storj/storagenode/gracefulexit.(*Service).ListPendingExits:59\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).AddMissing:58\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/storj/storagenode/gracefulexit.(*Chore).Run:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:44\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
Error: piecestore monitor: disk space requirement not met
2023-10-23 17:29:34,861 INFO exited: storagenode (exit status 1; not expected)
2023-10-23 17:29:35,864 INFO spawned: 'storagenode' with pid 45
2023-10-23 17:29:35,865 WARN received SIGQUIT indicating exit request
2023-10-23 17:29:35,865 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-10-23T17:29:35Z    INFO    Got a signal from the OS: "terminated"  {"Process": "storagenode-updater"}
2023-10-23 17:29:35,867 INFO stopped: storagenode-updater (exit status 0)
2023-10-23T17:29:35Z    INFO    Configuration loaded    {"process": "storagenode", "Location": "/app/config/config.yaml"}
2023-10-23T17:29:35Z    INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-10-23T17:29:35Z    INFO    Operator email  {"process": "storagenode", "Address": "mimi@mrblackcat.dev"}
2023-10-23T17:29:35Z    INFO    Operator wallet {"process": "storagenode", "Address": "0x5866c2cD552528875e263737e3Db1445d6237171"}
2023-10-23T17:29:35Z    INFO    server  kernel support for server-side tcp fast open remains disabled.  {"process": "storagenode"}
2023-10-23T17:29:35Z    INFO    server  enable with: sysctl -w net.ipv4.tcp_fastopen=3  {"process": "storagenode"}
2023-10-23 17:29:38,944 INFO waiting for storagenode, processes-exit-eventlistener to die
2

Hello @13MrBlackCat13,
Welcome to the forum!

and as a result

Please stop and remove the container, check and fix errors on the disk, then try to run the container back using all your parameters.
Then check logs again, if it still would not be able to open databases, you need to check and fix them:

You may also re-create only corrupted databases, but you will lose a history and the dashboard will show a wrong Stat:

3 

Running ./storagenode setup  --config-dir config --identity-dir identity --metrics.app-suffix=-alpha --metrics.interval=30m --version.server-address=https://version.storj.io --storage.allocated-disk-space=2.0TB 
2023-10-24T08:02:38Z    INFO    Anonymized tracing enabled      {"process": "storagenode"}
Error: open /app/config/config.yaml121848119: permission denied

Hello, this is the error when trying to reinstall, before I uninstalled all containers via docker system prune -a and decided to reinstall, but here is the problem.

Logs:


mimi@bravo-788:~$ sudo docker logs --tail 20 storagenode
2023-10-24T08:08:05Z    INFO    Got a signal from the OS: "terminated"  {"Process": "storagenode-updater"}
2023-10-24 08:08:05,642 INFO stopped: storagenode-updater (exit status 0)
2023-10-24 08:08:06,644 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
2023-10-24 08:08:08,068 INFO RPC interface 'supervisor' initialized
2023-10-24 08:08:08,068 INFO supervisord started with pid 1
2023-10-24 08:08:09,071 INFO spawned: 'processes-exit-eventlistener' with pid 12
2023-10-24 08:08:09,073 INFO spawned: 'storagenode' with pid 13
2023-10-24 08:08:09,075 INFO spawned: 'storagenode-updater' with pid 14
2023-10-24T08:08:09Z    INFO    Anonymized tracing enabled      {"Process": "storagenode-updater"}
2023-10-24T08:08:09Z    INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.89.5"}
2023-10-24T08:08:09Z    INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2023-10-24T08:08:09Z    INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-10-24T08:08:09Z    INFO    Operator email  {"process": "storagenode", "Address": "mimi@mrblackcat.dev"}
2023-10-24T08:08:09Z    INFO    Operator wallet {"process": "storagenode", "Address": "0x5866c2cD552528875e263737e3Db1445d6237171"}
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-10-24 08:08:09,121 INFO exited: storagenode (exit status 1; not expected)
4

You doesn’t need to run anything like that with the docker container. You need to use your full docker run command instead: Storage Node - Storj Docs

If you want to run it with a binary, you need to provide absolute paths to the identity and storage, also modify values like a wallet, email, external address in your config.yaml.
After that you may run it like

/opt/storagenode/storagenode run --config-dir /path/to/the/storage --identity-dir /path/to/the/identity/storagenode

but better to configure a service of course.

This is mean that you either provided a wrong path in the --mount option for the storage location or didn’t perform a SETUP step once (or may be you deleted data).

5

Did a complete reinstall and ended up with some complications, can I know if there is an api so I can get information from the deshboard through it?

6

What complications?