Ah it’s likely related to the forget sattelite. Somehow the forgetting of saltlake didn’t work.
I think there is still a bug in the forget sattelite mechanic. When I have saltlake in storage2.trust.exclusions it is not picking it in the forget command, even though it is in the config.yaml:
list of trust exclusions
storage2.trust.exclusions: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE@saltlake.tardigrade.io:7777”
When I do now:
docker exec -it STORJ-N ./storagenode forget-satellite --all-untrusted --config-dir config --identity-dir identity
STORJ-N for the docker-container it is stating:
root@server:~# docker exec -it STORJ-N ./storagenode forget-satellite --all-untrusted --config-dir config --identity-dir identity
2025-09-12T19:36:24Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2025-09-12T19:36:24Z INFO Invalid configuration file value for key {“Process”: “storagenode”, “Key”: “metrics.interval”}
2025-09-12T19:36:25Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2025-09-12T19:36:25Z INFO Identity loaded. {“Process”: “storagenode”, “Node ID”: “12Mio1W9tQTmfjnwRkozfAYKR2wnqfp8H9sLpGurLbG1tYV75GV”}
2025-09-12T19:36:25Z INFO No untrusted satellites found. You can add satellites to the exclusions list in the config.yaml file. {“Process”: “storagenode”}
It just works with:
docker exec -it STORJ-N ./storagenode forget-satellite --force 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE --config-dir config --identity-dir identity
Then you are getting the result:
2025-09-12T19:41:33Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2025-09-12T19:41:33Z INFO Invalid configuration file value for key {"Process": "storagenode", "Key": "metrics.interval"}
2025-09-12T19:41:33Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2025-09-12T19:41:33Z INFO Identity loaded. {"Process": "storagenode", "Node ID": "--"}
Satellite ID Status
1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE In Progress
You can then see it even in the logs file. Here the initializing:
2025-09-12T19:38:02Z INFO forgetsatellite:endpoint initializing forget satellite {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "action": "InitForgetSatellite"}
Then after some seconds:
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner removing satellite from trust cache {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner cleaning up satellite data {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner cleaning up the trash {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner removing satellite info from reputation DB {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner removing satellite v0 pieces if any {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2025-09-12T19:38:59Z INFO forgetsatellite:cleaner cleanup completed {"Process": "storagenode", "satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}