Not sure if everything is running correctly

Node Operators troubleshooting
1

Hi, I’m totally new to this.
I spun up a debian VM and mounted a NFS share from my nas to use with Storj.
Everything seems fine ish.

root@storjnode:~# docker exec -it storagenode /app/dashboard.sh
2023-12-30T22:37:52Z    INFO    Configuration loaded    {"process": "storagenode", "Location": "/app/config/config.yaml"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.wallet"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "storage.allocated-bandwidth"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.email"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "server.private-address"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "storage.allocated-disk-space"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "operator.wallet-features"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "healthcheck.details"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "console.address"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "server.address"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "version.server-address"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "healthcheck.enabled"}
2023-12-30T22:37:52Z    INFO    Invalid configuration file key  {"process": "storagenode", "Key": "contact.external-address"}
2023-12-30T22:37:52Z    INFO    Anonymized tracing enabled      {"process": "storagenode"}
2023-12-30T22:37:52Z    INFO    Identity loaded.        {"process": "storagenode", "Node ID": "12D7TwwVx9fiJB8ahfq55iXP7rqzwyqPLS5g41k6npVYyzDiTbn"}

This is just stuck until I do a ctrl+c
Checking through the ip:14002 it seems kinda fine.

image
image845×699 27.7 KB

Although I see no progress for bandwith.
But everytime I refresh the site the used storage goes up.
The built in refresh button just get stuck at updating the site as well, not really sure what’s up with that.

Also I started with 2G of RAM. Not sure what’s necessary but I bumped it up to 6G and it’s slowly climbing upwards. Currently sitting at 4,75G used.

Again freshly created Debian VM nothing else running except for the storj docker container.

2

Did you generate an identity? It is having an issue finding it, so it is either not there or maybe you didn’t allow the node to access it. We’ll help you get it working, not a problem.

3

First of all, NFS is not supported. Only iSCSI

Try to run the node on your nas directly. Wich one is it?

2 Likes
4

Ah I see, it’s a TrueNas Scale.
I’ll try setting up iSCSI and see how it works.

What should I do with my current node?

5

I did, pass it through in the docker run command. So should be no problems there.
But as daki82 said, NFS is not supported so I’ll give it a go with iSCSI.

Thanks so far!

1 Like
6

Generaly, the identity files and the node-data are already on the nas?
prepare the router and the nas to shut down the vm and install the node on the nas using the existing Identity and data.

Otherwise just start over with a newly generated identity(remove existing node data). At this state it doesn’t matter much wich way.

Or let it run with iscsi if you wish. (resources for the vm are wasted imho)
do what is easyer for you.

2 Likes
7

Hello @octal,
Welcome to the forum!

NFS and other network filesystems are not supported by storagenode and will stop to work sooner or later.
It’s better to run a docker container directly on your NAS instead.

They have a storagenode TrueChart, so you can run the node directly there.

1 Like