Changelog v0.33.4

Has the Docker container tag been changed from “beta”? What do we need to use? Beta tag does not seem to work. Gamma?

see above… 20 chars

1 Like

You should make a new topic for your issue. This seems to be unrelated to current topic.

Oh sorry, I thought that was referring to the number of installs per platform question before. Sorry.

@nerdatwork Really? That is the only thing here that you see unfit for this topic? During update, people will ask questions related to update in the topic that describes the update.

1 Like

@littleskunk
My node updated about 30 min ago, so far looks fine. I see only visual changes.
loogs looks fine. Any spesial test to do?
for now i updated 1 from over 15 GUI nodes

If the tag changed to something else it will probably be when they change it to released but far as I know its not in production yet so its still tag beta.

1 Like

Right, I thought so too but I mistunderstood/didn’t read properly what had Littleskunk said.

Im guessing docker hasnt gotten pushed the update yet?

My update on windows completed uneventful. Now, the new log reports does add a lot of data for each upload space available and bandwidth remaining.

What was the advantage for reporting these numbers on each upload? Is this permanent or just for testing?

Why not report those numbers in the same effect as the version report? LIke every 15 minutes.

I do like the new status bar and connection times.

2 Likes

Versioncontrol is now updated with a 10% rollout.

1 Like

please don’t get kill docker for Mac OS

Docker images are now pushed

2 Likes

manual update without a hitch, just curious does this setting have to be this precise (trust Scheduling next refresh {“after”: “4h25m25.599323941s”})

mine works fine too.

Updated as well. Previous dashboard looked a bit neater than this. This looks a bit too ordinary.

Hello,

i’ve uploaded manually, on storage-updater.log i have these warnings:

|2020-02-19T17:18:05.664+0100|INFO|Downloading versions from https://version.storj.io|
|---|---|---|
|2020-02-19T17:18:05.778+0100|INFO|New storagenode-updater version available but not rolled out to this nodeID yet|
|2020-02-19T17:24:41.701+0100|INFO|Stop/Shutdown request received.|
|2020-02-19T17:25:13.857+0100|INFO|Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: server.address|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: server.debug-log-traffic|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: storage2.max-concurrent-requests|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: operator.email|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: storage.allocated-bandwidth|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: server.private-address|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: contact.external-address|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: operator.wallet|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: storage.path|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file key: storage.allocated-disk-space|
|2020-02-19T17:25:13.898+0100|INFO|Invalid configuration file value for key: log.encoding|
|2020-02-19T17:25:14.055+0100|INFO|Downloading versions from https://version.storj.io|
|2020-02-19T17:25:14.549+0100|INFO|storagenode version is up to date|
|2020-02-19T17:25:14.549+0100|INFO|Downloading versions from https://version.storj.io|
|2020-02-19T17:25:14.664+0100|INFO|storagenode-updater version is up to date|

Why?

Because Invalid configuration file key: ...

Yes… but i did not edit the file…
It’s better if i restore the old version of sn and wait the auto update?

Thanks

I’ve just realized that this error was here before the manual update…

Docker image on arm platform auto-updated without issue :+1:

2 Likes