Version-related ingress block even though the latest version is installed

Hi,

Lately, I am often often seeing no ingress on my nodes when the storagenode version is older than 1-2 months.

However, I always keep the latest version (according to GitHub currently 1.41.2) installed. Installing one of the more recent pre-release version resolves this issue.

Am I supposed to be running pre-release versions? Or is the GitHub version marker out-of-sync?

According to Github the latest release they have makred as release candidate is 1.17.2.
However in my node it is already on version 1.73.4 which is marked as pre-release.
Just don’t trust the release version as it is not updated with every new release.
Also i suggest to run watchtower which updates it automatically.

You can find the current and rollout version here: https://version.storj.io/

"storagenode":{"minimum":{"version":"1.72.5","url":"https://github.com/storj/storj/releases/download/v1.72.5/storagenode_{os}_{arch}.zip"},
"suggested":{"version":"1.73.4","url":"https://github.com/storj/storj/releases/download/v1.73.4/storagenode_{os}_{arch}.zip"},
"rollout":{"seed":"b81496a1e67cdb9ce565db51ef434edddf039786b3cd2d718c4f465ce5e8b855",
"cursor":"a666666666666666666666666666666666666666666666666666666666666665"}}

You should have at least 1.72.5 right now. But 1.73.4 is being rolled out gradually and is already on the majority of nodes.

Safe yourself some time and use the updater. Versions are rolled out frequently and manual updating is really a chore.

4 Likes

Oh, so the version marker on GitHub it is out of sync indeed. If it is not updated regularly, it should probably be removed entirely.

Watchtower isn’t needed anymore. You can still run it but even without watchtower, the binary inside the docker image will get updated according to the rollout.

For my nodes (native without docker) I just run one storage-updater side by side with the storage node as systemd service.

True, but I still suggest running watchtower as well, as it would also update the container if that was updated. I believe the container updates have been taken out of the normal release cycle now, so you won’t get frequent unnecessary container updates anymore. But if something needs to change in the container scripts or base image, that will also be taken care of by watchtower.

3 Likes