Seeing this message in my Watchtower logs. Looking at prior posts it’s not clear what this is telling me: Watchtower believes there is an upgrade in progress (or an upgrade failed during an upgrade), node operator intervention may be required. (This feels like how I and many others are interpreti…

It will get an update when the time to come, you need to wait.

(I don’t see any logs attached?)

It’s literally just the following… 03/01/2025 8:20:37 AM time="2025-03-01T13:20:37Z" level=info msg="Waiting for running update to be finished..."

[image] cpare: It’s literally … been the case since day 1 of V3

@Alexey - Can you confirm this is a known defect. While I appreciate it may just be a red herring (and posted as an INFO, not WARN or ERROR), it’s something the community should know exists and can safely ignore until a watchtower developer can improve the case statement that’s resulting this confu…

I didn’t think watchtower was part of an install anymore: since the node performs its own internal upgrades? (like is this a message from a deprecated component?)

No, it’s not a known problem/bug, so must be something local.

Currently I am showing : v1.122.9 with “Your node is up to date. Current minimum version: v1.122.9” Is this what’s currently being deployed, or do I need to redeploy the watchtower container on my Ubuntu node? Also - @Roxor suggested watchtower is no longer needed - can anyone confirm?

I dont run watchtower and my nodes auto update

Looks like I have the latest container pulled down, I guess I need to make sure that’s the container version that’s deployed. sudo docker pull storjlabs/storagenode:latest [sudo] password for cpare: latest: Pulling from storjlabs/storagenode Digest: sha256:21ca0ac819d1d66240830d28097eeb693923e5…

Waiting for running update to be finished

Node Operators FAQ

nerdatwork March 11, 2025, 1:55am 13