Synology CLI Installed - FATAL Failed to load identity

i went and modified my config file, by downloading it and changing the Storage allowance and now its giving me this error when i try to show the dashboard

image

Its not an error but INFOrmation as the tag in the log clearly mentions it. You can safely ignore it.

You can also search the forum with the text you think is odd and get faster results too :slight_smile: In this case “invalid configuration file key”.

PS: its much better for others to see the text if you copy-paste it instead of screenshots. Your second post is not visible in the forum at all. When I open the image in another tab only then I can read it.

1 Like

sudo docker exec -it storagenode /app/dashboard.sh
2024-11-16T17:32:31Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “storage.allocated-bandwidth”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “healthcheck.details”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “operator.wallet-features”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “storage.allocated-disk-space”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “operator.wallet”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “console.address”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “healthcheck.enabled”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “server.address”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “contact.external-address”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “version.server-address”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “operator.email”}
2024-11-16T17:32:31Z INFO Invalid configuration file key {“Process”: “storagenode”, “Key”: “server.private-address”}
2024-11-16T17:32:31Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2024-11-16T17:32:31Z FATAL Failed to load identity. {“Process”: “storagenode”, “error”: “file or directory not found: open identity/identity.cert: no such file or directory”, “errorVerbose”: “file or directory not found: open identity/identity.cert: no such file or directory\n\tstorj.io/common/identity.Config.Load:326\n\tmain.cmdDashboard:77\n\tmain.newDashboardCmd.func1:49\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:271”}

it used to show how much storage i was using when i used the command

Check the path to the identity directory. Do you see 6 files in the identity folder ?

1 Like

Please show permissions for the identity location:

ls -l /path/to/the/identity

and for data:

ls -l /path/to/data

Also, if you run docker with sudo, you likely shouldn’t use --user $(id -u):$(id -g) in your docker run command.

Since you use docker, you should modify only parameter -e STORAGE to increase the allocation, it will override the value in the config file anyway, so it’s better to revert your changes in the config file. It could be also a reason, why it now cannot find the identity - you could corrupted the config.

Yes I got it working now, I had to redo the container via the GUI docker instead and now I can even view the dashboard,

1 Like