Audit Service Fix
On the storage node side you will still see audit failures but on the satellite side we only apply a penalty if we are sure it was not caused by one of the known bugs. We are interested to see how that works. Please keep an eye on your audit score. If your node is healthy you should see the reputation increasing even with audit failures in your log. If your audit score is decreasing please contact us.
Clock out of Sync
The time window for a valid upload is 1h (per segment!) We have added a new error message to the storage node log. If you see too many order created too long ago or order created too far in the future that usually means the storage node clock is out of sync.
Suggestion: plus 10% overhead to be allocated should be added to step 9’s installer screen.
Also in step 10. TB is hard coded for available disk space. A dropdown GB/TB would be nice with field rejecting anything below 500 when GB is selected.
I have been running the msi since0.20.1 on windows server 2016 as spare new drive not yet vetted but i have but docker down like a lame horse if it continues to improve like this this server will be colocated, i would like to auto update with out the need for a system reboot tho.
When storage path is given exactly as in the docker command, Windows GUI stores directly in that folder while docker command has it stored inside “storage” folder. This is why I was seeing zero stats for my node like it was new.
I understand that now but Windows GUI should behave same way docker did so its a smooth transition. I got 3 files stored outside storage folder because of this forcing me to revert back to docker.
Other files will be a database files, they can’t be moved without destroying the actual ones.
But you can carefully dump those databases and load those dumps to the actual databases respectively.
However those dumps must be cleared from sentences like drop database, drop table, etc. and from begin and rollback transactions before the load, almost as specified in the article:
