Because i got disqualified on 2 nodes, because of my internet providedr. They had an issue last night for few hours. Probably a lot of packet loss. It appears it happened during the night, so i couldn’t do anything. Previously it happened during the day and I just unplugged the cable from the node, but now I couldn’t. Why doesn’t STORj give us at least 24h to recover from any issue that we might have?
Anyway, I am very disappointed, i grew both of my nodes, for more that an year.
Thank you in advance!.
If you don’t let Storj know that there might be an issue then there is nothing they can do.
I think quick disqualfications are a problem. As SNOs are considered to be home users who might have family, a job and maybe even have to sleep somtimes, a disqualification should not happen within a couple of hours where a SNO cannot do anything to solve the issue because he might be sleeping.
So if we see these types of disqualifications more often then Storj might be willing to re-consider their approach.
I would actually recommend a support ticket. But they’re going to be rightfully quite critical about to what extent it may have been caused by an issue on Storj Labs end. If there wasn’t an issue on the satellite side, in all likelihood the disqualification will happen again at a later moment. So reinstating the node will not make sense. Even if you can promise the issue has been fixed on your end, Storj uses a trustless architecture and requires you to prove that on a new node.
By default you should assume your node will not be reinstated. In the example @jammerdan linked, they found out there was an issue on the satellite side that lead to the early disqualification of nodes. This is why it IS important to report it here when you think the problem may be on their end. But it’s also why it is highly unlikely your node will be reinstated if no issues on the satellite end are found.
I think the same. However, I think it is unfair as jammerdan said, because we have families. I was out all day yesterday. Came home, took a shower and went to sleep and found in this morning that may 2 nodes are disqualified on two satellites . Very unfair!!! It was probably a hung switch somewhere in my internet provider, because they fixed it in less than 10 minutes after i called. It’s a shame that there isn’t anything like a grace period. For example, if the network sees you giving false audit, it should suspend you for 24h or 48h, don’t know. But enough for you to resolve your problem. Or to get the node out of the network, for example unplug it, shut it down or something. After that time is passed the network could test the node and if it is good to permit it back in. Those disqualifications are … just a loss of time and data. Like me, I lost more than an year building them up.
Disqualification only happens if your node sent an error that the file is missing back to an auditing satellite or returns invalid data or fails to respond to the same audit 5 times in a row (within 5 minutes) while online (which causes a single audit failure). You would need to have at least about 10 audit failures in a row to be disqualified, more if they are spread out. In the case of time outs, that means timing out on a minimum of 50 audits.
All of these signal serious data reliability issues. Timing out on audits is probably the only one that doesn’t necessarily mean you’re missing or corrupting data. But imagine what would happen if nodes had a way to dodge audits like that? You get a lot of leniency by getting 5 chances to respond within 5 minutes before even a single failed audit is registered.
Therefor I have some doubts that this is caused by your ISP.
Furthermore, these rules aren’t about to change, so if the issues are on your ISPs side and you can’t do anything to resolve it, there is little use in reinstating your node as it will just run into that issue again.
Now I have argued for a more stable way of dealing with scores here: Tuning audit scoring
It got an initial positive response, but haven’t heard anything about it since. I’m guessing there are different priorities atm. That could possibly have saved you, but if they are not about to implement something like that, you’ll just hit the same wall again.
Generally data loss or corruption (or malice, but I wouldn’t accuse you of that). Disqualification doesn’t just happen. And when it happens it means the node is doing something seriously wrong.
Now that makes a whole lot more sense. Suspension happens when the issues are less clear. And luckily you can recover from that when the issues are resolved. It’s still worth looking at what caused it in the first place though. But not irreversible.