Prevent disqualify when moving storage path, new option

Node Operators
1

Hi all,

I’ve read so many tales of ‘moving to another path’ and then entering a wrong one, and getting disqualified.

For the love of all things that make sense, could Storj please put in a command line option;

--new-node This has to be run first to initialize a new storage path. The node will not start up in an empty location, unless this flag is entered. The node checks for a valid existing storage path unless this is specified. A log entry 'Proper storage path not found, wrong path specified, or something is seriously wrong! ABORTING' in the logs, if this flag is not specified and no correct folder found.

That way, no more stupid disqualifications because people make hones mistakes. And even experienced SNO’s make mistakes; why should the node even attempt to start in a ‘wrong’ location?

Please make this a priority to implement, it’s so simple it’s actually hurting that it isn’t implemented yet.

Thanks,
Martin

3 Likes
2

BrightSilence’s idea will likely solve also this problem, if it gets implemented.

1 Like
3

“Simple to implement, easy to understand fix” not implemented.

“Advanced fix to implement, less easy to understand, node stat dropping fix” still not implemented too.

Problem still relevant, based on SNO forum.

Guess which order I would prioritize implementing them in. I’m not saying the advanced fix doesn’t have a place, I’m just saying: maybe stop the fast, then add elegance? And… my guess: If the first fix is implemented, the second has 5% relevance less, because the causes remaining are esoteric compared to the ‘oops, wrote wrong path, killed the node, wanting to quit because i feel punished for a simple mistake’ problems.

4

Made a feature request:

2 Likes
5

And in the votable section of this forum; Prevent storagenode from starting in empty/invalid storage directory, unless explicitly stated