I will not lie - for a long time I misread exiting with existing!
But it still doesn’t explain why there seem to be unchanged activity with downloads, and exit-status of 0.00%
I can’t speak to activity, but for percent-complete the instructions say:
The “Percent Complete” field is a relic of the old graceful exit and is no longer meaningful. It will likely be removed at some point.
So I think it stays at zero and doesn’t move… then after 30 days hits 100%?
3 Likes
I will second that notion. Indeed how it works.
2 cents,
Julio
1 Like
Thanks all, i’ll assume i’m on the path for graceful exit - and check aggressively in 30 days (-;
1 Like
Okay maybe I missed it, but after I forget an untrusted node, will my data files clean themselves automatically? If so when? Or do I delete them manually"?
It will delete it if you used a --force option. It will not be a background deletion, it will wait for delete to be finished before complete the command and exit to the command prompt.
Other methods perhaps are background deletion, I didn’t check.
I believe it has changed again to /app/storagenode?
in addition, yeah I see how this time I used –force and it kicked off a seeming cleanup job. lots of disk activity and the commander gave me this message:
2025-08-26T22:28:54Z INFO Anonymized tracing enabled {“Process”: “storagenode”}2025-08-26T22:28:54Z INFO Identity loaded. {“Process”: “storagenode”, “Node ID”:
“1myBoZFvESJPwmwgKj9fNw95A91gs51Aqrh39xrgm6aUv17z1D”}Satellite ID Status12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S In Progress
Now it should be /app/bin/storagenode, since we have had an issue with executing binaries from the data location. Too many operators mounted storage without execution permission, so we fixed it by copying a binary from the data location to the /app/bin folder before start.
But if you use an old image, it may be still /app/storagenode
I have been kind of set it and forget it with the docker (compose) settings, and I’m a docker noob, but would docker compose pull update to new image?
Yep 
…………..(20)……..
2 Likes
Unfortunately, this only works temporarily for me, because the satellite comes back!
After executing the commands, the message disappears and everything seems to be fine.
But after a while, I receive an email saying that my node is back online on the satellite… Hmm?
And yes, the message is back again too 
You need also add it to the exclusion list, since the satellite is not removed from the trusted list, the node would contact it again, because now it does not remember (
), that’s disqualified on that satellite 
1 Like