Storage Node Update - Version available but not rolled out to this nodeID yet

Node Operators FAQ
1

Hello

Is this by design or is it something wrong?

|2020-04-07T13:03:25.099+0200|INFO|Downloading versions from https://version.storj.io
|2020-04-07T13:03:25.237+0200|INFO|New storagenode-updater version available but not rolled out to this nodeID yet

2

You are correct. This is to avoid all nodes going down at same time to update and files being left inaccessible. The only thing SNO can do is make sure storagenode-updater is running in services.

1 Like
3

Makes sense and that’s what I see in my log too, but I’ve had minimal traffic since April 14th 2020. It seemed like there was an update to 1.1.1 around that time that didn’t auto update. Is that related or is it because I’ve only got 400GB free on a 3TB STORJ drive?

FYI, here’s my log file

2020-04-25T10:16:24.980-0700 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2020-04-25T10:16:25.223-0700 INFO New version available but not rolled out to this nodeID yet {“Service”: “storagenode”}
2020-04-25T10:16:25.223-0700 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2020-04-25T10:16:25.278-0700 INFO Version is up to date. {“Service”: “storagenode-updater”}
2020-04-25T10:20:11.695-0700 INFO Stop/Shutdown request received.
2020-04-25T10:20:11.991-0700 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “operator.wallet”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “contact.external-address”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “operator.email”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “server.address”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “storage.path”}
2020-04-25T10:20:11.992-0700 INFO Invalid configuration file key {“Key”: “server.private-address”}
2020-04-25T10:20:11.992-0700 INFO tracing disabled
2020-04-25T10:20:12.074-0700 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2020-04-25T10:20:12.333-0700 INFO New version available but not rolled out to this nodeID yet {“Service”: “storagenode”}
2020-04-25T10:20:12.334-0700 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2020-04-25T10:20:12.393-0700 INFO Version is up to date. {“Service”: “storagenode-updater”}

4

More like your storagenode-updater service was not running.
But now you should wait, when the update will be available for your NodeID, and it will be updated automatically

5

Ok thanks I’ll leave it for a time and see if it updates. The updater is confirmed running now.

Maybe an issue can be raised about the notifications appearing to upgrade the node version when that update is not yet available to the node user?

6

Already raised multiply times:

1 Like