In the satellite logs we noticed that a few storage nodes are in a bad state and the storage node operators might not even notice it. Long term we will have to disqualify these storage nodes. To give the storage node operators a chance to avoid the disqualification we have added a storage node preflight check for the system clock and for the SQLite databases.
We are especially interested in 2 situation.
- It looks like docker on windows is unable to get the timezone from the host system. The storage node will run with a wrong clock. Please watch for log messages like
system clock is off: clock off by 2.01461. Is your system clock correct? If so please contact us with some additional information about your setup. Are you using windows or a different OS? Which docker version are you running? Any way to fix this issue? Is switching to the windows installer an option for you?
- The SQLite database check will catch schema mismatches as well. With v0.30.5 this check is disabled by default because we want to be sure it works as expected and doesn’t catch storage nodes by surprise. It will get enabled with the next release. Please use the time to test it on your storage node by adding
preflight.database-check: trueto your
config.yaml. Does it show any error messages? Is your storage node working if you disabled the check? I would call that a false positive and would like to know why this is happening.