My current node says v1.123.4. I received notices today saying that version was not upto date even though I have watchtower running and have never had this problem before. I logged in an tried to manually update the version but when I do it says the image is already upto date. This is what I get when I do a docker ps -a:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a58a369c4bb2 storjlabs/storagenode:latest “/entrypoint” 6 seconds ago Up 3 seconds 0.0.0.0:7777->7777/tcp, :::7777->7777/tcp, 0.0.0.0:14002->14002/tcp, :::14002->14002/tcp, 0.0.0.0:28968->28967/tcp, 0.0.0.0:28968->28967/udp, :::28968->28967/tcp, :::28968->28967/udp storagenode
09048c9810f0 storjlabs/watchtower “/watchtower storage…” 4 years ago Up 2 months watchtower
how, I tried doing the following but it says I am up to date:
storj@pine64-storj00:~$ storj-pull
latest: Pulling from storjlabs/storagenode
Digest: sha256:21ca0ac819d1d66240830d28097eeb693923e51383aa3bb07bf823f9fad1f6e9
Status: Image is up to date for storjlabs/storagenode:latest
docker.io/storjlabs/storagenode:latest
btw, storj-pull is an alias:
storj@pine64-storj00:~$ alias storj-pull
alias storj-pull='docker pull storjlabs/storagenode:latest'
what exactly should I be looking for in the logs? I’ve also done a docker exec -it storage node sh but I don’t see any logs there to look at or any commands/tools available in the image that would tell me anything about the dns (dig, nslookup, nmcli, etc.). In terms of time sync the image is UTC while my host is EDT but other than that there are no differences in the time.
ok, so I have no idea what happened but I did stop, removed, pulled with the same result. However, I subsequently rebooted and added my previous comments to this thread. I then left to do something and now that I am back I decided to check my not status in the UI. It now says I am at v1.125.2 and no longer reports that I am below the minimum version. Is this the current version? Again, I don’t know what fixed the problem but I assume maybe it was the reboot since that was the only thing I hadn’t tried previously.
I don’t get it… this link seems to indicate that 1.125.2 is the latest release. In which case I would be ok since that is there release I am not on. However, on that same page to the top right there is a drop-down called Compare that lists other newer releases (upto 1.127.2). Should one of those newer releases be the latest?
If you look at the page Alexey posted, with the “PLEASE READ this thread” link… you’ll see upgrade deployment rates are controlled by the node checking https://version.storj.io/. As of when I post this you’ll see the automated system is working through a 1.125.2 → 1.126.2 update.
Eventually all nodes will be told to be on 1.126.2… and when they think it’s appropriate… they’ll start pushing to 1.127.x (unless a major issue is found: they can always skip problem releases)
(The open-source tagged releases are one thing… and the system that slowly tells nodes to upgrade to certain versions is separate)
