Graceful Exit Guide

Product Discussions STORJLINGS
106

Holy S, I now have a message in dashboard ui to update the node lost on what to do now

107

Dont worry about it graceful exit will just start off where it stopped.

108

the status command is a bit vague as whether it has started or not

109

You will know when it starts, You will see it in the logs.

111

can a satellite be removed from the trust list during GE ie saltlake satellite

112

That satellite was recently introduced so the node being “old enough” won’t apply to it for GE, IMO.

113

I understand that but right now that satellite is still uploading and downloading while the other four satellites are working on GE and using resources on a failing hardware that will be power down at the end of GE, that is why I want to remove it from the trust list to stop it from using resources if that makes sense

114

GE takes time and your node has to respond to audits so you can’t turn off any satellite.

115

wow just realized the importance of the saltlake sat. but at the end of the GE when the hardware is shut down the node will be DQd and loose my remaining escrow anyway ?

116

Only small amount considering Saltlake is new

117

well when I started GE saltlake had close to 500 GBs of data

118

Some things mentioned here aren’t true. Satellites operate independently, so audits for saltlake would have no impact on the other satellites.

The node currently uses a url to determine which satellites are trusted, which makes it a bit harder to remove one. You can find it here https://tardigrade.io/trusted-satellites

You could host a text file with this list elsewhere and point the node to that. I’m not sure if you can also point it to a local file.

This is the config.yaml setting. Be sure to remove the # on the second line if you change it.

# list of trust sources
# storage2.trust.sources: https://tardigrade.io/trusted-satellites

Alternatively a really dirty way would be to simply remove the data from the saltlake satellite and your node will be disqualified on that satellite soon. But I personally wouldn’t go that route.

119

@BrightSilence well the reason I want to stop saltlake is because is to new for GE and before I launched GE it had already had received close to 450 GBs worth data and even now it’s very busy and it’s a waste of resources for a node that is going to be power down if the succeeds completing GE, thanks for reminding about the dirty way of ending my relationship with that satellite I have unintentional experience in earlier alpha

120

What I had to do is put allotted data to 0 so I would stop getting new data.

1 Like
121

Yes, that’s a better idea. It won’t stop downloads, but hey, that’s some extra pay anyway, so that may be ideal.

122

just were that allotted would go.
also I have noticed that “bandwidth usage rollups” is not being performed any longer.
how would that get me extra pay, unless due to the node being almost nine moths old there is no escrow left to payout.

123

Not sure what you’re trying to say here?

What makes you say that?

Downloads represent the largest part of earnings. Even during the first 9 months at least a part of that is paid out in your monthly earnings.

I’m not sure what you mean about there being no held back amount to pay out?

124

What makes you say that? well after starting GE I no longer see “performing bandwidth rollups” on the hour as before GE.
how would that get me extra pay, unless due to the node being almost nine moths old there is no escrow left to payout.
well forgot about 15 months held escrow.

125

@littleskunk I just completed GE on three of the 4 satellites that my node was eligible to GE from and I’m seeing europe-west-1 attempting to contact my node for pieces that were supposedly transferred to another storage node. Any idea on this? I do know that the update to v1.1.1 happened during GE, but I wouldn’t think that would kill the GE flag for the node. Example piece and output of exit-status attached. Figured you guys would want to know in case some edge case applies here.

2020-04-09T04:04:25.167Z ERROR piecestore download failed {“Piece ID”: “A4XWKSOALMWVLZOZ24DQZ7VTVLK4WVNQ24ELVG2UNQYGXL4J2WXA”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “GET”, “error”: “file does not exist”, “errorVerbose”: “file does not exist\n\tstorj.io/common/pb/pbgrpc.init.0.func3:70\n\tstorj.io/common/rpc/rpcstatus.Wrap:77\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doDownload:559\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Download:466\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func2:995\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:107\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:105\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:56\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:93\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51”}
aelita@StorjShare-VM:~/stearn$ docker exec -it storagenode /app/storagenode exit-status --config-dir /app/config --identity-dir /app/identity

Domain Name Node ID Percent Complete Successful Completion Receipt
satellite.stefan-benten.de:7777 118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW 1.59% N N/A
asia-east-1.tardigrade.io:7777 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 100.00% Y 0a483046022100daca4bef749f91e4fa7e8551140edfa6354cfb91304d27e360b0d3da9da0a0b1022100a9855ba23f3ae954426784b04eb67f4f6d815914872b65aac0aeb6ea991080e1122084a74c2cd43c5ba76535e1f42f5df7c287ed68d33522782f4afabfdb400000001a20ab40cf52fa4e691bc2c01b3d4b22df42c2d2e8d8fb5712e477ff49e6c0000000220c0898e7b8f40510e0a6f2e502
us-central-1.tardigrade.io:7777 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S 100.00% Y 0a473045022100aba624d4617f5469f9699bed06b0e684de04e8eb3fb7d60e10bcef6783ced53202207310cef08c429b93f1566b3866da95e1f3b61c5e4b46de67bb26ee4a1b052bb31220a28b4f04e10bae85d67f4c6cb82bf8d4c0f0f47a8ea72627524deb6ec00000001a20ab40cf52fa4e691bc2c01b3d4b22df42c2d2e8d8fb5712e477ff49e6c0000000220c0898e7b8f40510b0d29fc602
europe-west-1.tardigrade.io:7777 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs 100.00% Y 0a473045022100900b06928ba91c4e2b8ae107cd273f08f5465e859da3170dc5a3b65f468f68720220790a57b5882a729bd2cc1d0f543cf8bdd9d95cf62249a965738ea7f0b87cac921220af2c42003efc826ab4361f73f9d890942146fe0ebe806786f8e71908000000001a20ab40cf52fa4e691bc2c01b3d4b22df42c2d2e8d8fb5712e477ff49e6c0000000220c0898e7b8f4051098e6f1d302

126

Am I able to perform a graceful exit with a docker node on Windows? Running the command:

docker exec -it storagenode /app/storagenode exit-satellite --config-dir “D:\Storjv3-store” --identity-dir “C:\Users\user\AppData\Roaming\Storj\Identity\storagenode”

results in the error:

2020-04-09T15:28:30.285Z FATAL file or directory not found error: open C:\Users\user\AppData\Roaming\Storj\Identity\storagenode/identity.cert: no such file or directory

The path is correct, but notice how it is putting a forward slash between the path and the identity.cert file, which Windows therefore cannot parse.