Payout info matches except for disk average monthā¦ which shows a whole different wrong number compared to the other dashboard screenshotā¦ not sure where thatās coming from.
The most recent day shows 111.4TB*h, which is 4.6TB*d, significantly lower than the 5.29TB used. Seems like some of my nodes are underpaid for storage usageā¦ any idea how that is possible?
Thanks @BrightSilence, I just want to be sure of what is happening before I comment or do anything about this.
My quick guess is that the payout is probably still calculating using the tb*hā¦ So itās probably getting the total disk space used this month and dividing by (24*30) instead of just 30:
29.89TB*d / 30 = 996.33GBm 29.89TB*d / (24 * 30) = 41.51GBm (which reflects the wrong value on the payout info)
Some friendly advise for the future. Donāt use an existing variable and give it a different meaning. This wouldnāt have happened if you had simply calculated a B*d variable based on the existing one in a new variable.
LGTM
The other issue I outlined with some (many) of my nodes showing highly different numbers for TB*d compared to total stored is unrelated. Iāll create a different post around that.
It may not affect payouts, but for everyone graphing our nodes outputs, we now have an undetermined amount of time where those graphs will have incorrect values. While its only annoying, its very annoying.
My node on testnet is already running 1.67.3, which seems to have fixed this issue. 1.67.1 is currently being rolled out to production nodes. Itās possible 1.67.3 will make it to production nodes as well. In that case it might be sooner than the time between normal update releases. It just depends on whether Storj deems it important enough to publish a bugfix release for this. Perhaps @clement can enlighten us. But keep in mind itās the weekend now, so I donāt expect anything (release or response) until monday at the earliest.
I have just found that my nodeās estimated payout has dropped significantly after checking the dashboard today and after checking things out I realized my Disk Average Month has dropped incredibly low, from 60+tb/day to just 3-4tb/day, which resulted in the decrease of the payout. I have checked the data disk, the node and the logs, and is unable to find anything that indicate any problem.
Running docker logs storagenode 2>&1 | grep -E āGET_AUDIT|GET_REPAIRā | grep failed returns nothing, which I assume there is no problem with audit.
However, I do notice that there are yellow exclamation marks on all satellites, which might indicate something is wrong, but i couldnāt figure out exactly what is.
Will it affect my actual earning? Or the value that is displayed on the dashboard is purely for display and is different from the actual value that will be used to calculate my earnings?
Thank you.
EDIT: Thanks for merging the post. I now understand whatās going on.
Yep, I can confirm itās rolling out on one of my nodes as well. The same one that got the v1.67.1 update first. While some of my nodes still run v1.66.1. My guess is they restarted the rollout with the same seed, so nodes with v1.67.1 get fixed before nodes still on v1.66.1 get updated. Smart choice Iād say.
