AP1 keeps unsuspending a crashed and offline node

I guess it’s rare that someone complains about getting unsuspended, but late last year one of my (small) nodes failed due to a disk failure. Nothing too shocking, it’s actually the first disk failure I’ve had that led to a lost node and not using redundancy has paid for this failure many times over. However, for three times now, I have received an email to say this node was unsuspended on AP1, only to get a new suspension notification hours or days later. The node is offline and the data is lost. I have no clue what could cause the satellite to decide the node should be unsuspended. And this only seems to be happening with AP1.

If this keeps happening, my node will likely never be disqualified on AP1. And may even still trigger payout. (negligible, the node was 500GB total, so probably barely anything stored for AP1) Probably something you want to look into. Let me know if you want the node ID.

2 Likes

Well, AP1 (and EU1, with the other 2 surely soon to follow) just disqualified my node regardless. Still worth looking into the weird unsuspension messages though, I’d say.

Yes, please give its NodeID, I would ask the team.

Sent you a PM with the ID.

1 Like