when it happens, it will happen. Running fine without the update. I expect at XX:59 of the hour is when I usually see the update applied. maybe noon, 6pm, midnight or 6am the last few times. Yes, I am on windows.
1 Like
Is the update out yet? I do not want to keep restarting my node to check.
you do not forced to do so, just let it run
As I do not have automatic updates enabled (for reasons stated above), I have to check for updates manually. Normally, I see the new changelog and update my node, but this time the changelog is here, but no update.
You will see a warning in the log and then continuously restarting node, if your version is too dated
OK, Iāll look for that.
I guess it has not been pushed yet
It was announced to be a phased rollout starting with windows GUI nodes. The workweek hasnāt even started in the US. Monday was a holiday. Iām sure the first nodes will be updated through the course of the day, but it may take until the end of the week.
3 Likes
What Alexey meant was the point when you drop below the āoldest usable versionā threshold, not when you are 1 release behind.
just check for update once a day und youāll be fineā¦
this point is usualy 2 version behind.
The new binaries are now available. The plan is to start with 5% of the network. I donāt think the value of our versioncontrol is correct. Anyone gets the automatic update? I donāt think so. I know how to fix it but first I would like to get your feedback.
2 Likes
I must have been in the 5% my windows node updated, the log is reporting available bandwidth after a successful upload no new info on web dashboard
Ok that means my understanding of the versioncontrol is not correct and it works as expected. Thank you for the quick response.
Now back to the update process. We will keep the value at 5% for a few hours and watch for possible issues. Let us know if you see any problems. Later we will increase the value to 10%. We are currently not sure what later means. We will have to define what is needed to call the first 5% a success.
does anyone @ storj know what % of the 4800 snos are windows msi.
You can figure that our yourself: https://api.github.com/repos/storj/storj/releases
{
"url": "https://api.github.com/repos/storj/storj/releases/assets/17690346",
"id": 17690346,
"node_id": "MDEyOlJlbGVhc2VBc3NldDE3NjkwMzQ2",
"name": "storagenode_windows_amd64.exe.zip",
"label": null,
"uploader": {
"login": "littleskunk",
"id": 6333390,
"node_id": "MDQ6VXNlcjYzMzMzOTA=",
"avatar_url": "https://avatars0.githubusercontent.com/u/6333390?v=4",
"gravatar_id": "",
"url": "https://api.github.com/users/littleskunk",
"html_url": "https://github.com/littleskunk",
"followers_url": "https://api.github.com/users/littleskunk/followers",
"following_url": "https://api.github.com/users/littleskunk/following{/other_user}",
"gists_url": "https://api.github.com/users/littleskunk/gists{/gist_id}",
"starred_url": "https://api.github.com/users/littleskunk/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/littleskunk/subscriptions",
"organizations_url": "https://api.github.com/users/littleskunk/orgs",
"repos_url": "https://api.github.com/users/littleskunk/repos",
"events_url": "https://api.github.com/users/littleskunk/events{/privacy}",
"received_events_url": "https://api.github.com/users/littleskunk/received_events",
"type": "User",
"site_admin": false
},
"content_type": "application/x-zip-compressed",
"state": "uploaded",
"size": 9270514,
"download_count": 1289,
"created_at": "2020-01-30T19:37:30Z",
"updated_at": "2020-01-30T19:37:52Z",
"browser_download_url": "https://github.com/storj/storj/releases/download/v0.31.12/storagenode_windows_amd64.exe.zip"
},
Has the Docker container been updated?
No. We donāt have control over the docker update process. We will wait at least another 1-3 days before we push it.
1 Like
Ctrl + F5 does not help?
