Changelog v1.16.1

For Storage Nodes

Linux Auto Updates
We finished the Linux storage node updater and would love to get some help testing it. We are looking for storage node operators with the skill to manually create a service. Later down the road, we are going to publish a Linux installer and we also want to add the Linux updater to our docker container. So don’t worry if you can’t create a service file. This only means we will come back to you in one of the following test rounds. More information you can find here: [Tech Preview] Linux Storage Node & Updater

Downtime Tracking Enabled
We still had a feature flag from the old days and the audit service didn’t report back offline nodes. This is now fixed. We expect to see a good uptime score on the storage node dashboard.


Really cranking out the updates quickly these days!

1 Like

For the past 2 years or so!

1 Like

How many hours of downtime are allowed then?

I believe this means that downtime tracking has been enabled, but DQ for downtime has not. The current plan once DQ for downtime is enabled is to start with up to 288 hours of downtime before disqualification (although this is a simplification since there are other factors at play). The hours of allowed downtime is expected to be reduced as the system is optimized. See this post for more info:


Should everyone update or is running 1.15.3 fine to run for the next weeks?
I update manually so that’s no point for me…

1 Like

Couple of questions:

  1. Mostly out of curiosity, what’s the purpose of this new “secret.db” ?
  2. Downtime tracking, or as it’s displayed on dashboard “online” in percentage, is this just a running value, or is this based on a set period of time (i.e. per month and resets at the start of every month) or a rolling period of time (last 30 days)?
  3. Linux Auto Updates: this is an initiative to move the update functionality out of “watchtower” container and into the “storagenode” container (i.e. 2 containers down to 1?) I assume the idea is that it would help control the linux update roll out timing and prevent folks from not updating?