Windows node update Invalid configuration file key

Node Operators FAQ
1

I have 3 nodes. In every storage node logs I have this error:

2022-10-18T16:52:37.694+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “healthcheck.details”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “healthcheck.enabled”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “server.address”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “storage.path”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “operator.email”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file key {“Key”: “operator.wallet-features”}
2022-10-18T16:52:37.694+0200 INFO Invalid configuration file value for key {“Key”: “log.output”}
2022-10-18T16:52:37.711+0200 INFO Anonymized tracing enabled
2022-10-18T16:52:37.724+0200 INFO Running on version {“Service”: “storagenode-updater”, “Version”: “v1.64.1”}

2

Hi @agente
This is normal. It is from the storagenode-updater.log file. The storagenode-updater service uses the same config file as the storagenode service so the invalid configuration key INFO lines can be ignored.

3 Likes
3

i now have this error on my logs:

2023-05-03T12:21:08.320+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2023-05-03T12:21:08.399+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}
2023-05-03T12:21:08.399+0200 INFO Invalid configuration file key {“Key”: “healthcheck.details”}
2023-05-03T12:21:08.399+0200 INFO Invalid configuration file key {“Key”: “operator.email”}
2023-05-03T12:21:08.399+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}
2023-05-03T12:21:08.399+0200 INFO Invalid configuration file key {“Key”: “storage.path”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “healthcheck.enabled”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “operator.wallet-features”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “storage2.monitor.verify-dir-writable-interval”}
2023-05-03T12:21:08.401+0200 INFO Invalid configuration file key {“Key”: “server.address”}
2023-05-03T12:21:08.424+0200 INFO Anonymized tracing enabled
2023-05-03T12:21:08.445+0200 INFO Running on version {“Service”: “storagenode-updater”, “Version”: “v1.78.1”}
2023-05-03T12:21:08.445+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2023-05-03T12:21:10.047+0200 INFO Current binary version {“Service”: “storagenode”, “Version”: “v1.78.1”}
2023-05-03T12:21:10.047+0200 INFO Version is up to date {“Service”: “storagenode”}
2023-05-03T12:21:10.309+0200 INFO Current binary version {“Service”: “storagenode-updater”, “Version”: “v1.78.1”}
2023-05-03T12:21:10.309+0200 INFO Version is up to date {“Service”: “storagenode-updater”}