Hello to everyone,
I have installed the windows client and after the installation and the configuration I see that the service is started, but it stopped after a few seconds. The service is configured to start automatically, but it keeps staying down.
I also uninstalled the client and reinstalled, but nothing changed. I also rebooted the server and nothing changed.
Does anyone have any idea why is this happening or how could I solve it?
And in addition I’d like to ask if there is an option to change something on the settings afterwards or the only way is to uninstall it and re-install it.
With kind regards,
Angelos Pitsos
Do you have any log entries that might explain why it’s failing to start?
Hi @ACarneiro,
Thanks a lot for willing to help me. How can I get logs from STORJ windows client?
By default: C:\Program Files\Storj\Storage Node\storagenode.log
In the same folder you’ll find config.yaml which contains all the settings. After changing (and saving), you need to restart storagenode service.
Hey @mars_9t,
Thanks a lot for these useful clarifications!
here is the log file:
2023-05-11T12:48:37.679+0200 INFO Configuration loaded {"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "storage.path"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "healthcheck.details"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "healthcheck.enabled"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "storage.allocated-disk-space"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "operator.wallet-features"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "server.address"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "contact.external-address"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "storage.allocated-bandwidth"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "operator.email"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "operator.wallet"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file key {"Key": "server.private-address"}
2023-05-11T12:48:37.680+0200 INFO Invalid configuration file value for key {"Key": "log.output"}
2023-05-11T12:48:37.680+0200 INFO Anonymized tracing enabled
2023-05-11T12:48:37.682+0200 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T12:48:37.682+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T12:48:38.155+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T12:48:38.155+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T12:48:38.232+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T12:48:38.232+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T12:52:07.633+0200 INFO Got a signal from the OS: "terminated"
2023-05-11T12:54:10.504+0200 INFO Configuration loaded {"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2023-05-11T12:54:10.510+0200 INFO Invalid configuration file key {"Key": "contact.external-address"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "storage.allocated-bandwidth"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "operator.wallet-features"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "storage.allocated-disk-space"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "operator.wallet"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "operator.email"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "healthcheck.enabled"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "server.address"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "server.private-address"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "healthcheck.details"}
2023-05-11T12:54:10.511+0200 INFO Invalid configuration file key {"Key": "storage.path"}
2023-05-11T12:54:10.515+0200 INFO Anonymized tracing enabled
2023-05-11T12:54:10.521+0200 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T12:54:10.522+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T12:54:10.529+0200 ERROR Error retrieving version info. {"error": "version checker client: Get \"https://version.storj.io\": dial tcp: lookup version.storj.io: no such host", "errorVerbose": "version checker client: Get \"https://version.storj.io\": dial tcp: lookup version.storj.io: no such host\n\tstorj.io/storj/private/version/checker.(*Client).All:68\n\tmain.loopFunc:25\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tmain.cmdRun:136\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\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.ExecWithCustomConfigAndLogger:92\n\tstorj.io/private/process.ExecWithCustomConfig:74\n\tstorj.io/private/process.Exec:64\n\tmain.(*service).Execute.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-05-11T13:09:11.286+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T13:09:11.899+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T13:09:11.899+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T13:09:12.463+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:09:12.463+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T13:10:48.328+0200 INFO Stop/Shutdown request received.
2023-05-11T13:12:55.641+0200 INFO Configuration loaded {"Location": "C:\\Program Files\\Storj\\Storage Node\\config.yaml"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "healthcheck.enabled"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "healthcheck.details"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "storage.allocated-disk-space"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "operator.wallet-features"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "operator.email"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "contact.external-address"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "server.private-address"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "server.address"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "storage.allocated-bandwidth"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "storage.path"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file key {"Key": "operator.wallet"}
2023-05-11T13:12:55.642+0200 INFO Invalid configuration file value for key {"Key": "log.level"}
2023-05-11T13:12:55.643+0200 INFO Anonymized tracing enabled
2023-05-11T13:12:55.644+0200 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:12:55.645+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T13:12:56.114+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T13:12:56.114+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T13:12:56.192+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:12:56.192+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T13:27:55.663+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T13:27:56.153+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T13:27:56.153+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T13:27:56.231+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:27:56.231+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T13:42:55.678+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T13:42:56.163+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T13:42:56.163+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T13:42:56.226+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:42:56.226+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T13:57:55.689+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T13:57:56.190+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T13:57:56.190+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T13:57:56.253+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T13:57:56.253+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T14:12:55.707+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T14:12:56.193+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T14:12:56.193+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T14:12:56.272+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T14:12:56.272+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T14:27:55.711+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T14:27:56.180+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T14:27:56.180+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T14:27:56.259+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T14:27:56.259+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T14:42:55.714+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T14:42:56.198+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T14:42:56.198+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T14:42:56.276+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T14:42:56.276+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T14:57:55.747+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T14:57:56.217+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T14:57:56.217+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T14:57:56.295+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T14:57:56.295+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T15:12:55.748+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T15:12:56.232+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T15:12:56.232+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T15:12:56.310+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T15:12:56.310+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T15:27:55.760+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T15:27:56.261+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T15:27:56.261+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T15:27:56.340+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T15:27:56.340+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T15:42:55.773+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T15:42:56.257+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T15:42:56.257+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T15:42:56.335+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T15:42:56.335+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T15:57:55.782+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T15:57:56.267+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T15:57:56.268+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T15:57:56.345+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T15:57:56.345+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
2023-05-11T16:12:55.795+0200 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T16:12:56.266+0200 INFO Current binary version {"Service": "storagenode", "Version": "v1.76.2"}
2023-05-11T16:12:56.266+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode"}
2023-05-11T16:12:56.344+0200 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.76.2"}
2023-05-11T16:12:56.344+0200 INFO New version is being rolled out but hasn't made it to this node yet {"Service": "storagenode-updater"}
Can you understand what is wrong?
Hi all,
I found the problem. I was not allowing the outgoing traffic on the node.
I want to limit traffic to only the necessary doors. I noticed from the firewall logs outbound traffic on destination port 7777. Is this all the node needs or are there other ports I should allow?
With kind regards,
Angelos Pitsos
storagenode uses p2p communications (data is transferred directly between your node and the customer, which can have any IP and any port), so you should allow to connect to any host and any port from your PC or do not have any outbound rules enabled.
You need to allow to connect from any host and any port to the TCP 28967 and UDP 28967 ports and IP of your PC.
Please do not specify the source port in any firewall rules, because they can be literally any. Basically you should not have any outbound rules or disable them or create another one to allow to connect to any address and port from your PC. And you need only two allowance inbound rules - for TCP and UDP ports of your node.
If you would like to connect to your dashboard from other devices you may use How to remote access the web dashboard - Storj Node Operator Docs or [Tech Preview] Multinode Dashboard Binaries
To troubleshoot the issue, check the SRORJ client’s log file located at “C:\Program Files\Stroj\Storage Node\storagenode.log” for any error messages. Regarding changing settings, you can modify the “config.yaml” file in the same folder and restart the storagenode service.