Stuck on 0.33.4?

Is 0.33.4 the most recent version? I feel like watchtower has stopped working. I tried manually pulling but am still getting 0.33.4. Am I doing something wrong?

Thanks

The new update is getting rolled out slowly. You don’t need to manually update it. Make sure your watchtower is working properly.

Ah ok. Hopefully mine will come up soon. Has an email been going out to specific users who can update?

1 Like

No, not need to. The watchtower (or storagenode-updater on Windows) should be running, this is enough.

2 out of 3 Windows nodes are updated to 0.34.6
Will a notification be released when Windows node updates are done?
I still have one Windows Node on 0.31.12.
Both services are running.

do you have only 1 node on windows?

No, I have 3 Windows nodes.
2 of them are updated to last version.
1 is on 0.31.12

try to restart updater

@Vadim I´m Microsoft Systems Administrator :smiley:
Those were my first steps:
Rebooting computer
Checking Updates pending
Services running, etc…

My output log says it´s not rolled out to my node yet:

2020-03-09T11:18:14.598Z INFO New storagenode-updater version available but not rolled out to this nodeID yet
2020-03-09T11:23:14.087Z INFO Stop/Shutdown request received.
2020-03-09T11:23:16.141Z INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: server.address
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: storage.allocated-bandwidth
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: storage.allocated-disk-space
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: contact.external-address
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: operator.wallet
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: storage.path
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: operator.email
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: server.debug-log-traffic
2020-03-09T11:23:16.152Z INFO Invalid configuration file key: server.private-address
2020-03-09T11:23:16.152Z INFO Invalid configuration file value for key: log.encoding
2020-03-09T11:23:16.292Z INFO Downloading versions from https://version.storj.io
2020-03-09T11:23:16.923Z INFO New storagenode version available but not rolled out to this nodeID yet
2020-03-09T11:23:16.923Z INFO Downloading versions from https://version.storj.io
2020-03-09T11:23:17.061Z INFO New storagenode-updater version available but not rolled out to this nodeID yet

StorageNode output:

2020-03-09T10:16:15.574Z INFO piecestore download started {“Piece ID”: “PQIDDQTMMM3VRI5OGRLT2YB57WDM6W4RPPKNCQUQGJX4HVD4VTWA”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET_AUDIT”}
2020-03-09T10:16:15.758Z INFO piecestore downloaded {“Piece ID”: “PQIDDQTMMM3VRI5OGRLT2YB57WDM6W4RPPKNCQUQGJX4HVD4VTWA”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET_AUDIT”}
2020-03-09T10:25:28.196Z INFO bandwidth Performing bandwidth usage rollups
2020-03-09T10:25:28.780Z INFO version running on version v0.31.12
2020-03-09T10:30:10.802Z INFO orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE sending {“count”: 1}
2020-03-09T10:30:10.802Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs sending {“count”: 1}
2020-03-09T10:30:10.968Z INFO orders.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2020-03-09T10:30:11.357Z INFO orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE finished
2020-03-09T10:40:28.750Z INFO version running on version v0.31.12
2020-03-09T10:55:28.727Z INFO version running on version v0.31.12
2020-03-09T11:10:28.817Z INFO version running on version v0.31.12
2020-03-09T11:10:57.654Z INFO piecestore download started {“Piece ID”: “URQUTYUAAFQFTCLDKURJBAU7DZPCCXELO45VS3WFJSUPCP3V262A”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Action”: “GET_AUDIT”}
2020-03-09T11:10:57.921Z INFO piecestore downloaded {“Piece ID”: “URQUTYUAAFQFTCLDKURJBAU7DZPCCXELO45VS3WFJSUPCP3V262A”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “Action”: “GET_AUDIT”}
2020-03-09T11:16:34.651Z INFO Stop/Shutdown request received.
2020-03-09T11:18:08.550Z INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-03-09T11:18:08.592Z INFO Operator email: xxxxxxxxxxxxx@gmail.com
2020-03-09T11:18:08.592Z INFO operator wallet: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2020-03-09T11:18:09.318Z INFO version running on version v0.31.12
2020-03-09T11:18:09.327Z INFO db.migration Database Version {“version”: 31}
2020-03-09T11:18:10.200Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-03-09T11:18:11.135Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-03-09T11:18:11.139Z INFO bandwidth Performing bandwidth usage rollups
2020-03-09T11:18:11.140Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 19999226062336}
2020-03-09T11:18:11.146Z INFO trust Scheduling next refresh {“after”: “4h33m17.286168893s”}
2020-03-09T11:18:11.146Z INFO Node 12rAzVA7GB3TnnURDME6iqgyvsT8mnr7KJqzqmKgSRdqvFooWtN started
2020-03-09T11:18:11.146Z INFO Public server started on [::]:28967
2020-03-09T11:18:11.146Z INFO Private server started on 127.0.0.1:7778
2020-03-09T11:18:11.277Z INFO version running on version v0.31.12
2020-03-09T11:18:36.511Z INFO orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE sending {“count”: 1}
2020-03-09T11:18:37.045Z INFO orders.1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE finished
2020-03-09T11:23:10.422Z INFO Stop/Shutdown request received.
2020-03-09T11:23:12.496Z INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-03-09T11:23:12.527Z INFO Operator email: xxxxxxxxxxx@gmail.com
2020-03-09T11:23:12.528Z INFO operator wallet: 0xxxxxxxxxxx
2020-03-09T11:23:13.214Z INFO version running on version v0.31.12
2020-03-09T11:23:13.229Z INFO db.migration Database Version {“version”: 31}
2020-03-09T11:23:14.140Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-03-09T11:23:15.082Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-03-09T11:23:15.082Z INFO bandwidth Performing bandwidth usage rollups
2020-03-09T11:23:15.082Z INFO trust Scheduling next refresh {“after”: “5h4m12.121700132s”}
2020-03-09T11:23:15.082Z INFO Node 12rAzVA7GB3TnnURDME6iqgyvsT8mnr7KJqzqmKgSRdqvFooWtN started
2020-03-09T11:23:15.082Z INFO Public server started on [::]:28967
2020-03-09T11:23:15.082Z INFO Private server started on 127.0.0.1:7778
2020-03-09T11:23:15.086Z INFO piecestore:monitor Remaining Bandwidth {“bytes”: 19999226062336}
2020-03-09T11:23:15.220Z INFO version running on version v0.31.12

but Storagenode-updater.log?

1 Like

Go up in my post, it’s the first one.

Finally updated :smiley:
Huge difference on traffic, much more pieces!

1 Like

Still no Docker containers tho.

I guess you mean 0.34.6.

1 Like

Edited, thanks :wink: Yup, no Docker updates…yet.
I´m curious to see how this will affect on my RPI nodes.

2 Likes

Same here - no docker update yet… We’ll see. Please let us know at what point all should be updated, from what I see watchtower is fine (updated it last time) and didn’t restart / check update on purpose.

1 Like

Hi, I’m alway in v0.33.4 it’s normal ?

the docker release is not slated to go out until at least tomorrow

4 Likes

Just received an e-mail from StorjLabs telling me I should update my Node because it still in v33.4. My watchtower did not update anything yet though. I checked, it’s running. In fact, I stopped, removed and recreated it to be sure (like 10 minutes ago), but for the moment nothing’s happening.

Is there anything wrong with my watchtower, or was this e-mail notice sent too early by StorjLabs?

1 Like

Watchtower updates randomly between 72 hours.

docker release v0.34.6 out now. I updated my Synology 1 hour ago