We have read it multiple times that mount points are breaking, were done wrong after moving a node or replacing the harddrive. This often results in the nodes being DQed for missing pieces. This is my proposal to solve this problem: When the node starts, it checks in with the satellite. Now withou…

https://review.dev.storj.io/c/storj/storj/+/2272

For logs written to a file tail -f /volume1/storj/v3/data/node.log | awk '/(ERROR|canceled|failed).*GET_AUDIT/ {system ("docker stop -t 300 storagenode")}' For logs in docker docker logs -f --tail 20 storagenode | awk '/(ERROR|canceled|failed).*GET_AUDIT/ {system ("docker stop -t 300 storagenode"…

i suppose one could just set it so that if it gets two failed audits in the 1min per log append then it would shut it down and trigger an alert. and if need be increase it to two or 5 minutes per append to give it more overview… ofc that comes at slower reaction time. thanks ill give it a try som…

not bad but I opened this suggestion so we won’t need solutions like that in the future :smiley:

Oh absolutely. It’s not a solution and it can never be as good as the node software doing it itself. And besides only a small fraction would only read something like this on a forum. Your suggestion is still very valid.

well one simple option might be to extend the already growing docker run command… xD that might simply be to update the storj documentation website, when we have a workable command… which buys storj time to bake in a solution.

We currently have work in progress to add a new preflight check to storagenodes that will prevent them from starting if they have not selected the correct storage directory. We discussed a variety of ways to implement it, but it seems like the most practical thing to implement for now is the followi…

Also make the node check for the existence of that file every minute or so. If it disappears - crash.

[image] moby: When the node is restarted in the future, it will check the storage directory for this new file. If the file does not exist, it will assume the mount point for the storage directory was incorrectly configured and fail to start. how would it know that it isnt a new node?

We haven’t determined the best way to do it yet, but we’ve discussed a couple options: If there are 0 pieces stored when the node is starting up, add the file Run a special command when a new mount point is used that will add the file. After the first time, a different command should be used I gu…

Thanks for the suggestion. I added this point to the ticket.

Storj Community Forum (official)

Prevent broken mount points from DQing nodes

Ideas & Suggestions Storage Node feature requests - voting