Disqualified on one satellite

Hi guys,

sorry to bother on the " Sat, 05 Sep 2020 05:48:11 GMT" my node was disqualified on the 3 satellites. :worried:

I checked the logs and see thous errors. Please see the attached picture.
To be honest when COVID start. I had one intervention when Linux partition was full.
I do not check the logs. Since that Seagate HDD case. No suspensions I was thinking all good.
Errors referring to the "ERROR piecestore download failed " are on the satellite I’m currently not disqualified. So I scare to get disqualified on them as well.

Is that serious, do I need to start from the beginning. :sob:

All those errors do not affect the audit rate.
Please, search for GET_AUDIT and failed in the same line. Your node can fail audits only if:

  • the piece is unavailable (file not found);
  • the piece is corrupted or hash is wrong;
  • timeout 4 times in row for the same piece.

All other GET_AUDIT errors could only suspend your node.

Hi Alexey. I checked all of the logs and do not see GET_AUDIT and failed in the same line.
Can I send the logs on priv or any other option to check why I got disqualified?

Please, give me your NodeID, I’ll ask the team to look into logs of the satellites.

Hi Alexey,

Node ID:

Thank you.

Hi all,

Dont want to open a new thread since it is related. I just got a message that my node is disqualified on the stefan Satellite.

What does this mean now?

The node has about 4TB of data. Should I wipe it and set up a new node? Or just let it run and accept the fact that stefan disqualified me :slight_smile:

Any way to find out why the node got disqualified? The email I got is not very informative…

Stefen is going to be shut down if that’s the only satellite you got dqed on I wouldn’t worry about it.

1 Like

Hello @krilson,
Welcome to the forum!

Because of failed audits. Please, check your logs and search for GET_AUDIT and failed to see a reason. Also, the audit will be treated as failed if you have GET_AUDIT and download started, but not downloaded at the end. And of course, if audited piece is exist but corrupted, the audit will be treated as failed too. If audit score fall below 0.6 (60% on the dashboard), the node will be disqualified.

Hi @Alexey, thank you for the warm welcome.

I checked the logs, but I only see logs since the last restart. And I restarted the node after getting this disqualified notice.

Is there a log archive somewhere to be found?

I checked the logs using:

docker logs storagenode >& storjshare.log

And then searching this file. Did not find any “failed” entries.

Edit: I tried opening the web dashboard now for the first time (used the CLI dashboard only before).

I see these entries near the top:

Your node has been disqualified on 118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs .

For example, opening the stefan satelite shows:

So it got disqualified on 24.March 2020. But I got this email notification on 15.September (yesterday). Is this normal? Such a delay in the notification…

Upon further inspection I see that I got disqualified from all but one satelite. All on the same date 24.March 2020.

They all have the same audit score of 59.9%

The one satelite that is ok is: europe-north-1.tardigrade.io:7777, it has both scores 100% 100%.

Is this all normal? I apologize for being a bit confused. I set and forget this node a while ago with watchtower updates, only monitoring the CLI dashboard. Seeing that it was storing data and using bandwidth I assumed that everything is ok with the node.

Looks like your got DQed on every satellite. This is probably because of a bad mount or you moved nodes to another hard drive, and didnt start with the right location of the data.

I did extend the partition. The node is running on a VM and I increased the disk size.

But all seemed well, same mount point and all the files are intact.

So should I wipe it and start as a new node now? Im a bit confused, since europe-north-1.tardigrade.io:7777 is ok.

What is the smart move here?

I would try and run a graceful exit on europe-north, assuming you have made the 6 month minimum and the amount held is worth it to you. Then start over with a new node. EU-North is probably fine because it didn’t exist until April of this year.

1 Like

Could be a matter of time before it is too DQed possible has less data so it would take longer to DQ at this point.

I would just cut my losses and start over, EU north isnt worth saving a node for.

I have about 200$ in reserved. That seems worth it. The node is older than 6 months.

But I might be forced to leave it behind. Gracefull exit doesnt work, gives no useful feedback on what the error is… I posted it here: Graceful Exit Guide

You dont have 200 held for EU north.do you?..Maybe 200 total my eu node only has 5dollars held considering eu north is one of the newest satellites… But im pretty sure the highest held amount was stefen which you should have already gotten back?

You are right, on EU north I have held 25$, the rest is on stefan, about 178$

Interesting that by storage used over 90% is on EU north (4tb used altogether, eu north holds 3.8tb, the rest of the satelites, which are all disqualified hold a few gb or even mb each).

So this held amountof 178$ on stefan is as well as gone for me now? I cant do anything about it?

Well Did you check your wallet to see if you got a higher payout then normal, I would check there first you may have already gotten it. Less you node was offline before the payout happened?

It’s disqualified March, 24. Five months ago.
@krilson Unfortunately all held amount from those satellites is used to recover the lost data.

@Alexey ok, tnx for the info. And everyone else for the help.

I wiped it and created a new node now. :slight_smile:

1 Like

It was disqualified for too much download timeouts during audits. Your node was unable to provide a few kb with 5 minutes timeout for audit. With 4x attempts for each audited piece.