Updating to v 1.53.1

So this just happened failed to update to 1.53.1 instead it reinstalled 1.52.2 again about 4 times.

> 2022-04-20 23:49:56 (194 MB/s) - written to stdout [84/84]
> --2022-04-20 23:49:56--  https://github.com/storj/storj/releases/download/v1.52.2/storagenode_linux_amd64.zip
> Resolving github.com (github.com)...
> Connecting to github.com (github.com)||:443... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/128089774/1bd10c0f-982c-482a-a490-6e5860e789f2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220420%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220420T234956Z&X-Amz-Expires=300&X-Amz-Signature=02aa08c0cbabd92de306055b8cc28455adf12128d993df904f0e02ca8d90e310&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=128089774&response-content-disposition=attachment%3B%20filename%3Dstoragenode_linux_amd64.zip&response-content-type=application%2Foctet-stream [following]
> --2022-04-20 23:49:56--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/128089774/1bd10c0f-982c-482a-a490-6e5860e789f2?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220420%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220420T234956Z&X-Amz-Expires=300&X-Amz-Signature=02aa08c0cbabd92de306055b8cc28455adf12128d993df904f0e02ca8d90e310&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=128089774&response-content-disposition=attachment%3B%20filename%3Dstoragenode_linux_amd64.zip&response-content-type=application%2Foctet-stream
> Resolving objects.githubusercontent.com (objects.githubusercontent.com)...,,, ...
> Connecting to objects.githubusercontent.com (objects.githubusercontent.com)||:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 15675435 (15M) [application/octet-stream]
> Saving to: '/tmp/storagenode.zip'

2022-04-20 23:49:55 (200 MB/s) - written to stdout [92/92]

--2022-04-20 23:49:55--  https://github.com/storj/storj/releases/download/v1.52.2/storagenode-updater_linux_amd64.zip
Resolving github.com (github.com)...
Connecting to github.com (github.com)||:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/128089774/7cc525c9-8b78-4199-98e6-861239e6b4f4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220420%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220420T234954Z&X-Amz-Expires=300&X-Amz-Signature=f6db666789fb35bb53684d1229ebdbf038fec2fe38d995722b55a641a97f37c6&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=128089774&response-content-disposition=attachment%3B%20filename%3Dstoragenode-updater_linux_amd64.zip&response-content-type=application%2Foctet-stream [following]
--2022-04-20 23:49:55--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/128089774/7cc525c9-8b78-4199-98e6-861239e6b4f4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20220420%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220420T234954Z&X-Amz-Expires=300&X-Amz-Signature=f6db666789fb35bb53684d1229ebdbf038fec2fe38d995722b55a641a97f37c6&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=128089774&response-content-disposition=attachment%3B%20filename%3Dstoragenode-updater_linux_amd64.zip&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)...,,, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8106329 (7.7M) [application/octet-stream]
Saving to: '/tmp/storagenode-updater.zip'

It also restarted my node everytime as well an triggered a filewalker…

1 Like

no problem with my single node that has updated, its using linux amd64.
but haven’t checked the logs and don’t think this particular node is logging more than 1mb :smiley: so
its gone…

it is nice to see that, it actually didn’t update all of them at once like last time lol

how to update? or wait auto-update?
im using windows 11

it will update itself at some point, they don’t want all nodes to go offline at the same time.
for obvious reasons :smiley:

This seems like a similar updater issue.

Anyone running watchtower beware of this,
When theres a new update it will try to update the node but not actually update it an it will restart the node as if it was updated. All of my nodes had this happen and none of them have updated.

> time="2022-04-22T06:55:32Z" level=info msg="Found new storjlabs/storagenode:latest image (sha256:73fa3c53b16ba099852a6058d2149114b4a7492f743a5029c7063933dfa4f53e)"
> time="2022-04-22T06:55:33Z" level=info msg="Stopping /storagenode (b4ce11799d8ab594d380a03417d45eab799fec0ddba8a31f1768808b0fb108b1) with SIGTERM"
> time="2022-04-22T06:55:54Z" level=info msg="Creating /storagenode"

1 Like

Sounds like expected behaviour if your node hasn’t been reached by the rollout yet. It just happens to be that they pushed a container update and a node update around the same time. Going forward I believe we are expecting far fewer container updates than node software updates.


Can you explain how its expected behavior? A unnecessary restart shouldnt be something you expect.

I think it’s expected based on how the update system has worked historically. I agree that unnecessary restarts are a problem, but this seems like a growing pain more than anything else. In theory we could reach a point where the base image is never updated, and therefore restarts due to watchtower updating the container will never happen. Of course it is not likely that there will never be a base image update, but storjlabs themselves have stated that the goal is to update the base image as little as possible, and let the internal updater do all the work.


I guess its ok if it restarts, But then they need to stop making filewalker trigger with every restart of the node cause thats just alot of load for the drives, that dont need every single time.


Agreed. It would be nice to have the node recognize how long it’s been since the last filewalker routine and only run if it hasn’t been run in the last 72 hours or something like that. Perhaps a user configurable variable.

1 Like

I am happy, that watchtower was not working for me anymore, so I’ve switched it off a while ago. Hope the update will work for me without issues. :v:t2: