How to deal with partial disqualification

It seems that SNO can encounter a situation where they are partially disqualified from the network.

I discovered this thing by deep inspecting my logs because aside that I have a constant flow of operations (PUT/GET/GET_AUDIT)

2019-07-10T08:57:53.902Z INFO vouchers Requesting voucher {“satellite”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”}
2019-07-10T08:57:54.000Z INFO vouchers Requesting voucher {“satellite”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2019-07-10T08:57:54.000Z INFO vouchers Requesting voucher {“satellite”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2019-07-10T08:57:55.626Z INFO vouchers Voucher request denied. Node does not meet voucher requirements: ANY (disqualified?, total audit count, total uptime check count)
2019-07-10T08:57:56.995Z INFO piecestore:orderssender.12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S finished
2019-07-10T08:57:57.262Z INFO vouchers Voucher request denied. Node does not meet voucher requirements: ANY (disqualified?, total audit count, total uptime check count)
2019-07-10T08:57:58.162Z INFO vouchers Voucher request denied. Node does not meet voucher requirements: ANY (disqualified?, total audit count, total uptime check count)
2019-07-10T08:57:58.531Z INFO piecestore:orderssender.12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs finished
2019-07-10T08:58:17.122Z ERROR piecestore:orderssender.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to receive response: rpc error: code = Unavailable desc = transport is closing
2019-07-10T08:58:17.122Z INFO piecestore:orderssender.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW finished
2019-07-10T08:58:17.122Z ERROR piecestore:orderssender.118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW failed to settle orders {“error”: “order: failed to receive response: rpc error: code = Unavailable desc = transport is closing”, “errorVerbose”: "order: failed to receive response: rpc error: code = Unavailable desc = transport is closing
2019-07-10T08:58:32.683Z INFO piecestore upload started {“Piece ID”: “TZO6N2NI4WHHZU47C3DOR7NYTXGRDTA4I5B5OZ5IHJ3LFSWOTNFQ”, “SatelliteID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “PUT”}
2019-07-10T08:58:34.964Z INFO piecestore upload started {“Piece ID”: “G66AMQIXZ4TEJOUZMEG22A5257SRI3N6AN45IICGJ6GFEFLME2QQ”, “SatelliteID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “PUT”}

So it seems that the satellite “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW” still consider me healthy, while the others are not.
Question time:

  • How this condition can happen ?
  • What’s the strategy suggested here from Storj team ? Should I just abandon the node and start a new one from scratch ?
  • Why Satellite are not synching the status of the SN between them ?

Easy. You lost pieces exactly of those satellites. Or because your node has been saturated by requests and was unable to respond on audit request four times sequential.

My opinion - start from scratch. If your node is disqualified.
Messages about voucher just means that your node still in the vetting process.

Because they are independent of each other.

2 Likes

I might be wrong, but I think you’ve likely just not been vetted by the three smaller satellites yet. Not necessarily disqualified.

@Alexey I’m I misreading something here?

Note: These timestamps are prior to the release of the new version with better log lines for unvetted nodes.

No, you are right @BrightSilence.

These messages doesn’t means that your node is disqualified @Droddo. It could be in the vetting process.
But my answers are still valid.

1 Like

I don’t disagree with your answers. Just making sure @Droddo doesn’t kill his node based on this. I think it’s still fine. :slight_smile:

1 Like

What does it mean? Remove all data with container and setup new one or generate new key?

Generate a new key, sign it with a new authorization token, remove the old data and run a new node.

2 Likes