I had 7 out of 24 Not vetted now it is down to 2 of 24. The two remaining ‘Not vetted’ is both on saltlake.
1 Like
All except one fixed as well.
Details of the missing:
12KiYpvzm9YwhJBx6LtQufCEae1zk42sAYDpX8FtnEAieeBV1k1
1 Like
Not vetted on Saltlake does almost not matter. It’s around 5GB of data per node at this time 
2 Likes
True, but for transparency and StorJ evaluating the success of their fix, it might be relevant.
And its fixed for me, thanking you, looks like EU vetting status now sorted here.
Well done StorJ
And may now be seeing more ingress from EU
CC
1 Like
I think it’s a better to leave it as is to check that the bug is fixed, when the issue would be worked out. However, I’m not sure, that it would be applied to the past nodes though, depends on what’s a bug and how we would fix it.
Will the fix be applied to saltlake as well ? I have two nodes not vetted at saltlake both older than a year: 12u9Sbesa5nAtmLCc1yu7p51qQhTqb2fb3mzS3bNpXcvZonshpE and 12oNsFhs6G6wNFFMQCuw3MNzpANtnNvnZM5eApVDFLufqaeE5Aj
The other nodes I had that was not vetted at eu1 and ap1 is ok now 
If I were Storj, given saltlake is not worth much in node revenue, I’d use saltlake as an opportunity to test proper fixes for this problem. A one-time database sync is not a fix, because the problem might show up again. It’s just a quick patch.
1 Like
We executed the query for saltlake after we didn’t have any objection.
@Toyoo had a good point, but because we can already observe some unalignment, we didn’t have the need to keep saltlake unsync for continue investigating it. Anyway, thank you for point it out.
2 Likes
This is an ubuntu node running version 1.132.7. My older windows node from 2019 shows status as vetted. I have other windows nodes from early 2023 which also do not show vetted.
Is something wrong?
1 Like
I’m actually kinda sad this bug was discovered, I considered it a leg up on competition. Oh well, there are others.
2 cents,
Julio
1 Like
Currently i have satellite us1 not vetted, however by using the estimator.py script (Earnings calculator (Detailed earnings info and health status of your node, including vetting progress and garbage collection status)) i see that have done 10324/100 Audits.
Is there any way to fix that?
Hello @contix93,
Welcome to the forum!
It will be fixed when a bug will be fixed. All what we did - is used a workaround, it’s not a permanent solution.
But you can try the workaround on your side, however, it’s risky:
Be careful if you would like to do that. It’s not a solution, it’s a risky workaround. Your node could be disqualified pretty fast.
As this bug is still not fixed - how often is this workaround being executed?
Our apologies, we haven’t fixed it yet.
The workaround isn’t executed periodically.
TL;DR
We have done some investigations and we continue it in between higher priority tasks, but so far we haven’t found where is the bug.
We thought, as also commented from some SNOs that could be because we don’t execute the both database tables updates in a transaction, however, we couldn’t confirm it after adding a metric to detect the unalignment.
On the other hand, The workaround isn’t executed periodically. We executed the bulk once (or perhaps twice) and we have executed some manual updates for some SNOs who has reported it through a support ticket.
2 Likes
Thanks for the update; I just thought it would make sense to execute the workaround like e.g. once a month until there’s a fix, so that new operators have the same chance as the oldies.
So far we haven’t done it because knowing a specific unalignment may provide insides on the changes and investigations that we are conducting.
We talked about to executing periodically, but we haven’t reach a determination yet.
Hello there !
So I rebuilt my entire storj node after a full crash. It’s been 45 days that it is operational. Saltlake.tardigrade.io is OK but the others ap1, eu1 and us1 are still not vetted, despite their huge amount of audits.
What am I doing wrong here ?
