CLI Dashboard no longer working on nodes updated to v1.77.2

Node Operators
1

I just got a bit of a scare when I noticed a lot of my CLI dashboards had stopped. Version 1.77.2 seems to no longer be able to find the identity.

$ docker exec -it storagenodetest /app/dashboard.sh
2023-04-21T12:39:18.329Z        INFO    Configuration loaded    {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "contact.external-address"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "server.private-address"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "identity.key-path"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "server.use-peer-ca-whitelist"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "storage2.trust.sources"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "storage.allocated-disk-space"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "operator.wallet-features"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "operator.wallet"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "server.address"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "operator.email"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "storage.allocated-bandwidth"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "version.server-address"}
2023-04-21T12:39:18.329Z        INFO    Invalid configuration file key  {"Process": "storagenode", "Key": "identity.cert-path"}
2023-04-21T12:39:18.329Z        INFO    Anonymized tracing enabled      {"Process": "storagenode"}
2023-04-21T12:39:18.330Z        FATAL   Failed to load identity.        {"Process": "storagenode", "error": "file or directory not found: open : no such file or directory", "errorVerbose": "file or directory not found: open : no such file or directory\n\tstorj.io/common/identity.Config.Load:326\n\tmain.cmdDashboard:80\n\tmain.newDashboardCmd.func1:49\n\tstorj.io/private/process.cleanup.func1.4:399\n\tstorj.io/private/process.cleanup.func1:417\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomOptions:113\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:79\n\tmain.main:26\n\truntime.main:250"}
2 
$ docker exec -it storagenodetest cat /app/dashboard.sh
#!/bin/sh

./storagenode dashboard --config-dir /app/config --identity-dir /app/identity $@

$ docker exec -it storagenodetest ls /app/identity
ca.1635924092.cert  ca.key                    identity.cert
ca.cert             identity.1635924092.cert  identity.key

It’s definitely there. And this still works fine on all my nodes still running v1.76.2.

3
2 Likes
4

Ahh, thanks. I should have checked github.

The nodes work fine otherwise luckily.

1 Like
5
1 Like
6

Oof… I thought I searched for it… sorry about the double post. My searching skills have failed me.

7

That’s officially 2 of us now.