Node version tool old for QA sattelite

Node Operators troubleshooting
,
1

I have received an email saying that my node version is too old for the QA satellite, which is weird because I keep automatic updates enabled on that node. Still, I tried to update the node manually, but it did not update.

2024-03-15T21:10:59Z    INFO    Running on version      {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.95.1"}
2024-03-15T21:10:59Z    INFO    Downloading versions.   {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2024-03-15T21:11:00Z    INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.95.1"}
2024-03-15T21:11:00Z    INFO    New version is being rolled out but hasn't made it to this node yet     {"Process": "storagenode-updater", "Service": "storagenode"}
2024-03-15T21:11:00Z    INFO    Current binary version  {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.95.1"}
2024-03-15T21:11:00Z    INFO    New version is being rolled out but hasn't made it to this node yet     {"Process": "storagenode-updater", "Service": "storagenode-updater"}

Is that correct?

2

Seems you need to check that your --version.server-address option/setting is pointed to the:

3

It is


# server address to check its version against
#version.server-address: https://version.storj.io
version.server-address: https://version.qa.storj.io
# if true, uses peer ca whitelist checking
server.use-peer-ca-whitelist: false

# list of trust sources
storage2.trust.sources: 12nErpw5894bSadEPfYLc4PJQ6ZuFHNhqhXHTAYdPsSzBrNcUiX@de-tube.ddns.net:10000,1GGZktUwmMKTwTWNcmGnFJ3n$

  File: config.yaml
  Size: 9841            Blocks: 24         IO Block: 4096   regular file
Device: 801h/2049d      Inode: 24772612    Links: 1
Access: (0600/-rw-------)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-03-17 16:49:35.588542114 +0200
Modify: 2022-07-11 23:53:42.457596551 +0300
Change: 2022-07-11 23:53:42.457596551 +0300
 Birth: -

And it was like that since 2022

Checking old logs, I see that the updater has always used https://version.storj.io and not the correct one.

The satellite list works though, so it has to read the file.

4

@littleskunk could it be related to a 1.100.x version and the alphabetic sorting?

5

Unfortunately for docker nodes, the VERSION_SERVER_URL flag overrides the value in the config, and the default is set to https://version.storj.io. You would have to explicitly set the VERSION_SERVER_URL to https://version.qa.storj.io in your docker run command:

docker run ...
-e VERSION_SERVER_URL="https://version.qa.storj.io"
4 Likes
6

That fixed it, thank you.

1 Like